lf-decentralized-trust-labs/cbweb3/speckit-bug-fix

Fix Bug

Apply the remediation that was proposed by /speckit.bug.assess and record the changes in a fix report at .specify/bugs/<slug>/fix.md. This command is only valid after an assessment exists for the given slug.

User Input

$ARGUMENTS

The user input should identify the bug to fix. Accept any of:

• slug=<bug-slug> or --slug <bug-slug> or just 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.bug.assess, the slug it reported is the working slug. Reuse it without re-prompting. Confirm it by checking that .specify/bugs/<slug>/assessment.md exists; if it does not, fall through.
3. Single candidate on disk — list .specify/bugs/*/assessment.md. If exactly one matching assessment.md is found, use the slug from its parent directory.
4. Disambiguate:

• Interactive mode: ask the user which bug to fix and list the candidates.
• Automated mode: stop with an error listing the candidates. Do not guess.

Once resolved, set BUG_SLUG and BUG_DIR = .specify/bugs/<BUG_SLUG>, and briefly state which resolution path was used.

Prerequisites

• BUG_DIR/assessment.md MUST exist. If it does not, stop and instruct the user to run /speckit.bug.assess first.
• If BUG_DIR/fix.md already exists, ask the user whether to overwrite it (interactive mode) or refuse (automated mode).
• Read BUG_DIR/assessment.md in full. Treat its Proposed Remediation, Files likely to change, Tests to add or update, and Risks & Considerations sections as the contract for this command.

Execution

1. Confirm the plan — Restate in 3–6 bullets what will be changed and where, based on the assessment. If verdict is invalid, stop. If likely valid, needs reproduction with unresolved [NEEDS CLARIFICATION] items, flag them and ask in interactive mode, or stop in automated mode.

1. Apply the remediation:

• Make the code changes described by the preferred remediation. Stay within the files listed by the assessment unless newly discovered evidence requires expanding scope (log any expansion explicitly).
• Add or update the tests called out in the assessment so the bug cannot regress silently.
• Keep the change minimal — do not refactor unrelated code, do not introduce dependencies not called for by the assessment.
• If you discover the assessment was wrong, STOP modifying code, document the new finding in the fix report under Deviations from Assessment, and recommend re-running /speckit.bug.assess.

1. Run local checks — If the project has obvious test commands (e.g., go test, pytest, npm test), run the tests that exercise the changed paths. Capture pass/fail and key output. Do not run destructive or network-dependent suites without the user's consent.

1. Write the fix report to BUG_DIR/fix.md:

```markdown # Bug Fix: <short title>

• Slug: <BUG_SLUG>
• Fixed: <ISO 8601 date>
• Assessment: ./assessment.md
• Status: applied | partial | not-applied

## Summary

<One or two sentences describing what was changed and why.>

## Changes

## Tests Added or Updated

• path/to/test_file.py::test_name — <what it pins down>

## Local Verification

• Commands run: <command> → <result, brief>
• Manual checks: <what was verified by hand, if anything>

## Deviations from Assessment

<Empty if none. Otherwise, list any places where the actual fix departed from the proposed remediation and why.>

## Follow-ups

• <suggested cleanup, monitoring, doc update, etc.>

```

1. Report back with slug, BUG_DIR/fix.md path, status (applied, partial, not-applied), and next suggested step: /speckit.bug.test slug=<BUG_SLUG>.

Guardrails

• Never modify files outside the project workspace.
• Never edit assessment.md — it is the contract. Record disagreements in fix.md under Deviations from Assessment.
• Never delete files unless the assessment explicitly required it.
• Never overwrite an existing fix.md without confirmation.