97 tagged bdd, measured the same way as everything else here.
Browse within: clean-architecture 24github-copilot 24acceptance testing 23ai-development 23atdd 23golang 14bdd-framework 13test 13test-driven-development 13agentic 9qa 9gherkin 7api-testing 6bruno 6
Skill Claude CodeCodex
Diagnose a failing Ginkgo suite as an agent — always run with --json-report into a predictable temp/gitignored location, read the terminal verdict line, then use jq to extract structured failure details (name, message, file:line, panic value, captured logs). Covers the panicked-vs-failed trap, panic locations pointing…
Skill Claude CodeCodex
Run Ginkgo suites with the ginkgo CLI — run, -r, -p, --dry-run, watch, build (precompiled .test binaries), generate, outline, unfocus, labels, version; spec randomization (--randomize-all/--randomize-suites/--seed); running multiple suites (--keep-going/--skip-package/--compilers); previewing (--dry-run…
Skill Claude CodeCodex
Parameterize and generate Ginkgo specs — DescribeTable/Entry table-driven specs, Entry descriptions (string, nil, closure, EntryDescription), PEntry/FEntry and per-Entry decorators, DescribeTableSubtree, generating specs in a construction-time loop, loading fixtures in TestXxx before RunSpecs, and shared-behavior…
Skill Claude CodeCodex
Use to drive a bug fix from first report through close, with a "why didn't we catch it?" loop at the end. Triggers — "/engineer.fix", "a bug came in", "this is broken", "a user reported X", "there's a defect", "we have a regression", "this needs a fix", "another report", "more issues", "still failing", "validation…
Skill Claude CodeCodex
Use at the start of a work session, or any time the question is "what should I pick up now" across the whole project. Triggers — "/engineer.next", "what's next", "what should I work on", "what should I do next", "where do I pick up".
Skill Claude CodeCodex
Use to add a third validation layer to the ATDD workflow — after acceptance tests verify WHAT and unit tests verify HOW, mutation testing verifies the tests actually catch bugs. Triggers — "/mutate", "/kill-mutants", "run mutation testing", "mutate my code", "kill mutants", "check test quality", "find surviving…
Skill Claude CodeCodex
Generate a draft story markdown by analyzing a story tracker or feature description, Figma designs, and the codebase.
Skill Claude CodeCodex
Interactive guidance on why human code review is essential for readability and maintainability.
Skill Claude CodeCodex
Execute BDD test scenarios from .feature files using browser automation.
Skill Claude CodeCodex
Samurai scoped testing framework for Go (github.com/zerosixty/samurai). MUST use when writing, modifying, reviewing, or debugging Go tests that import samurai, or reference samurai.Run, samurai.RunWith, samurai.Scope, samurai.TestScope, samurai.W, or samurai.BaseContext.
Skill Claude CodeCodex
Autonomous quality engineering swarm that forges production-ready code through continuous behavioral verification, exhaustive E2E testing, and self-healing fix loops. Combines DDD+ADR+TDD methodology with BDD/Gherkin specifications, 7 quality gates, defect prediction, chaos testing, and cross-context dependency…
SebastienDegodez/skraft-plugin
Skill Claude CodeCodex
Use when creating, refreshing, expanding, or reviewing a SKRAFT Vally skill evaluation at tests/skills/ /eval.yaml in the skraft-plugin repository. Covers behavior coverage, baseline-versus-isolated-treatment discrimination, natural prompts, outcome rubrics, non-activation cases, regression guards, fixtures, static…
SebastienDegodez/skraft-plugin
Skill Claude CodeCodex
Use this skill BEFORE drafting any agentic primitive module (skill, persona scoping file, scope-attached rule file, orchestrator workflow) or when refactoring an existing one. Activate whenever the task asks to design, restructure, or critique an agentic module across any agent harness (Claude Code, Copilot, Cursor…
SebastienDegodez/skraft-plugin
Skill Claude CodeCodex
Use when selecting architecture patterns for a new feature, performing Event Modeling, defining bounded contexts, choosing DDD tactical patterns, evaluating pattern fitness, or understanding how patterns compose. Covers Event Modeling methodology, DDD strategic design, DDD tactical patterns, Clean Architecture, CQRS…
Skill Claude CodeCodex
Use this skill to run the Shipshape Captain role: human-facing discovery, durable specs and assets, Captain-only notes, blocker resolution, and outbound decisions. Default entry for new product intent and any user conversation.
Skill Claude CodeCodex
Use this skill to understand the Shipshape workflow, shared Articles of Agreement, and select the correct role skill: /captain, /qm, /crew, /boatswain, or /shipwright. Entry point when no role is active or the right role is unclear.
Skill Claude CodeCodex
Use this skill to run the Shipshape Shipwright role: in-harbour code inspection. Discovers existing behaviour and policy violations from production code, writes @captain-tagged scenario skeletons and @planks annotations for Captain review. Run for fitting out, onboarding an existing codebase, and between releases.
burugo/behavior-driven-development
Skill Claude CodeCodex
Use when implementing any feature or bugfix, before writing implementation code. Triggered by keywords: TDD, BDD, test-first, test-driven, write-test-first.
burugo/behavior-driven-development
Skill Claude CodeCodex
Use in a dedicated subagent when completing tasks, implementing major features, or doing post-TDD code review before merge to verify work meets requirements.
burugo/behavior-driven-development
Skill Claude CodeCodex
Use in a dedicated subagent for post-TDD blind unit-test review against requirements and public contracts to find missing cases, wrong assertions, and brittle tests.
Skill Claude CodeCodex
Run a spec-driven correction loop for code that already exists by comparing the current implementation against the spec and using linter output, test failures, runtime logs, and review feedback to diagnose and fix gaps. Use this whenever code is failing checks, drifting from acceptance criteria, regressing after…
Skill Claude CodeCodex
Capture and retrieve durable project memory for spec-driven engineering, including decisions, constraints, setup steps, root causes, fixes, patterns, and reusable snippets through lightweight local indexing and keyword retrieval. Use this whenever the user wants to save knowledge for later, look up prior solutions…
Skill Claude CodeCodex
Turn ambiguous software requests into BDD-style implementation-ready specs with clear scope, constraints, assumptions, acceptance criteria, validation steps, execution guardrails, and an implementation plan. Use this whenever the user is defining requirements, asking for a plan or spec, wants boundaries clarified…
seekdevcore/sk-requirements-engineering-theskill
Skill Claude CodeCodex
Use when doing requirements engineering, business analysis, or the software-engineering stage of discovering / specifying / validating / managing requirements — the stage BEFORE code (what to build) and AFTER (was the right thing built?), for new projects and for evolutions of existing ones. Triggers (EN)…