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-verify)<a href="https://agentmods.dev/commands/pimzino/claude-code-spec-workflow/bug-verify"><img src="https://agentmods.dev/badge/commands/pimzino/claude-code-spec-workflow/bug-verify/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-verify"><img src="https://agentmods.dev/badge/commands/pimzino/claude-code-spec-workflow/bug-verify.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.00812 |
| Opus 5.5 | $0.00000 | $0.00325 |
| Sonnet 5.5 | $0.00000 | $0.00162 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
bug-verify 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-verify — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Verify Command
Verify that the bug fix works correctly and doesn't introduce regressions.
Usage
/bug-verify [bug-name]
Phase Overview
Your Role: Thoroughly verify the fix works and document the results
This is Phase 4 (final) of the bug fix workflow. Your goal is to confirm the bug is resolved and the fix is safe.
Instructions
You are working on the verification phase of the bug fix workflow.
-
Prerequisites & Context Loading
- Ensure the fix has been implemented
Load ALL Context Once (Hierarchical Context Loading):
# Load bug templates for verification structure claude-code-spec-workflow get-template-context bugBug documents to read directly:
.claude/bugs/{bug-name}/report.md.claude/bugs/{bug-name}/analysis.md- Understand what was changed and why
- Have the verification plan from analysis.md
-
Verification Process
-
Original Bug Testing
- Reproduce the original steps from report.md
- Verify the bug no longer occurs
- Test edge cases mentioned in the analysis
-
Regression Testing
- Test related functionality
- Verify no new bugs introduced
- Check integration points
- Run automated tests if available
-
Code Quality Verification
- Review code changes for quality
- Verify adherence to project standards
- Check error handling is appropriate
- Ensure tests are adequate
-
-
Verification Checklist
- Original Issue: Bug reproduction steps no longer cause the issue
- Related Features: No regression in related functionality
- Edge Cases: Boundary conditions work correctly
- Error Handling: Errors are handled gracefully
- Tests: All tests pass, new tests added for regression prevention
- Code Quality: Changes follow project conventions
-
Create Verification Document
- Template to Follow: Use the bug verification template from the pre-loaded context above (do not reload)
- Document all test results following the bug verification template structure
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 · 118 lines · 0 tokens per session scan A 1f0ca5cb0981
bug-verify 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 812 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
playwright-test-heal
Run all my tests and fix the failing ones.
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
api-aqa-flow-execution-and-report-analysis
Phase 6 Execution & Report Analysis of api-aqa-flow (USER INTERACTION REQUIRED).
timeout-fix
A procedure for diagnosing and fixing tests that exceed their time limit by finding causes such as slow processing, hanging network calls, deadlocks, heavy setup, or leaked resources.
AGENTS
Run the current binary in a temporary test repository with a real PTY. Use tmux-cli when available, capture terminal output, and inspect -vv logs when behavior depends on timing or shell state. Avoid treating a piped command as proof of interactive behavior.