speckit.bug.test
Checks that a recorded fix resolves the bug described in the assessment, and writes a verification report.
- Kind
- Prompt
- Works with
- Claude Code, Codex, GitHub Copilot, Cursor, Windsurf / Devin, Cline
- Source
- github/spec-kit @ c00dc0551583
- Path
- extensions/bug/commands/speckit.bug.test.md
- License
- MIT
- Jobs
- Testing
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
# Test Bug Fix Validate that the fix recorded by `__SPECKIT_COMMAND_BUG_FIX__` actually resolves the bug described by `__SPECKIT_COMMAND_BUG_ASSESS__`. The output is a verification report at `.specify/bugs/<slug>/test.md`. ## User Input ```text $ARGUMENTS ``` The user input should identify the bug to validate. Accept any of: - `slug=<bug-slug>` or `--slug <bug-slug>` or a bare slug-like token. - A path that contains the slug (e.g. `.specify/bugs/login-timeout/`). - **Nothing** — fall back to context (see below). ## Slug Resolution Resolve `BUG_SLUG` in this order, stopping at the first match: 1. **Explicit user input** — a slug passed in `$ARGUMENTS` (any of the forms above). 2. **Conversation context** — if the current session has just run `__SPECKIT_COMMAND_BUG_ASSESS__` or `__SPECKIT_COMMAND_BUG_FIX__`, the slug it reported is the working slug. Reuse it without re-prompting. Confirm it by checking that `.specify/bugs/<slug>/fix.md` exists; if it does not, fall through. 3. **Single candidate on disk** — list `.specify/bugs/*/fix.md`. If exactly one bug has a `fix.md`, use it. 4. **Disambiguate**: …