What is speckit.bug.fix?

A bug-fixing command that applies the remedy proposed in a previous bug assessment and records what changed.

Use it to apply an assessed remediation for a selected bug and save the fix report for later verification.

It keeps implementation tied to an earlier diagnosis and leaves a written record of the fix.

speckit.bug.fix — Command by github

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/github/spec-kit/speckit.bug.fix

Clone the repo

git clone --depth 1 https://github.com/github/spec-kit

Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,301 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00012	$0.01301
Opus 5	$0.00006	$0.00651
Sonnet 5	$0.00002	$0.00260
Haiku 4.5	$0.00001	$0.00130

Measured yesterday against content hash df8b28b36876, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

speckit.bug.fix scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

speckit.bug.fix — 100% identical, 0 lines differ

extensions/bug/commands/speckit.bug.fix.md · 113 lines

How it starts

The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Fix Bug

Apply the remediation that was proposed by __SPECKIT_COMMAND_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:

Explicit user input — a slug passed in $ARGUMENTS (any of the forms above).
Conversation context — if the current session has just run __SPECKIT_COMMAND_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.
Single candidate on disk — list .specify/bugs/*/assessment.md. If exactly one matching assessment.md is found, use the slug from its parent directory.
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 in your reply which resolution path was used (explicit / from context / single candidate / asked).

Prerequisites

BUG_DIR/assessment.md MUST exist. If it does not, stop and instruct the user to run __SPECKIT_COMMAND_BUG_ASSESS__ first.
If BUG_DIR/fix.md already exists, ask the user whether to overwrite it before continuing (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.

Read the full file on GitHub · 113 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 113 lines · 12 tokens per session scan A df8b28b36876

Subscribe to this mod's changes

speckit.bug.fix is a command published in the GitHub repository github/spec-kit (132,298 stars, last pushed 3d ago), licensed MIT. It adds 12 tokens to every session and 1,301 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Debugging Planning ai copilot development engineering prd spec

speckit.bug.fix

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

How it starts

Fix Bug

User Input

Slug Resolution

Prerequisites

What this file has done since we first saw it

Other commands, from other repositories

book-internalize

book-style

stardust-session

book-characters

book-formula

stardust-list