Claude Code Spec Workflow is a collection of automated workflows that guides Claude Code through feature development and bug fixing. Developers use it to move from requirements to design, tasks, and implementation, or from a bug report through analysis, fixing, and verification, with the catalogue providing its commands and specialized agents.
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.
git clone --depth 1 https://github.com/Pimzino/claude-code-spec-workflowWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/pimzino/claude-code-spec-workflow/bug-fix)<a href="https://agentmods.dev/commands/pimzino/claude-code-spec-workflow/bug-fix"><img src="https://agentmods.dev/badge/commands/pimzino/claude-code-spec-workflow/bug-fix/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/pimzino/claude-code-spec-workflow/bug-fix"><img src="https://agentmods.dev/badge/commands/pimzino/claude-code-spec-workflow/bug-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00000 | $0.00792 |
| Opus 5.5 | $0.00000 | $0.00317 |
| Sonnet 5.5 | $0.00000 | $0.00158 |
| Haiku 4.5 | $0.00000 | $0.00079 |
Grade A, and why
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 1mo ago.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- bug-fix — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Fix Command
Implement the fix for the analyzed bug.
Usage
/bug-fix [bug-name]
Phase Overview
Your Role: Implement the solution based on the approved analysis
This is Phase 3 of the bug fix workflow. Your goal is to implement the fix while following project conventions.
Instructions
You are working on the fix implementation phase of the bug fix workflow.
-
Prerequisites & Context Loading
- Ensure analysis.md exists and is approved
Load ALL Context Once (Hierarchical Context Loading):
# Load steering documents (if available) claude-code-spec-workflow get-steering-contextBug documents to read directly:
.claude/bugs/{bug-name}/report.md.claude/bugs/{bug-name}/analysis.md- Understand the planned fix approach completely
-
Implementation Process
-
Follow the Implementation Plan
- Execute changes exactly as outlined in analysis.md
- Make targeted, minimal changes
- Follow existing code patterns and conventions
-
Code Changes
- Implement the fix following project standards
- Add appropriate error handling
- Include logging or debugging aids if needed
- Update or add tests as specified
-
Quality Checks
- Verify fix addresses the root cause
- Ensure no unintended side effects
- Follow code style and conventions
- Run tests and checks
-
-
Implementation Guidelines
- Follow steering documents: Adhere to patterns in tech.md and conventions in structure.md
- Make minimal changes: Fix only what's necessary
- Preserve existing behavior: Don't break unrelated functionality
- Use existing patterns: Leverage established code patterns and utilities
- Add appropriate tests: Ensure the bug won't return
-
Testing Requirements
- Test the specific bug scenario
- Verify related functionality still works
- Run existing test suite if available
- Add regression tests for this bug
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.
- 1mo ago First seen · 121 lines · 0 tokens per session scan A ad44367edf9d
bug-fix is a command published in the GitHub repository Pimzino/claude-code-spec-workflow (3,859 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 792 tokens. 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.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
react-native
Command "react-native" from getsentry/toolkit, covering examples, also associate with a release and distribution(s), xcode build step (react-native xcode) and important notes.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.