A command that starts a tracked workflow for fixing a bug. The workflow separates reporting, investigation, implementation, and verification into four phases.

It creates a bug folder and initializes documents for the report, root-cause analysis, fix, and verification.

It keeps a small bug fix organized without requiring the larger process used for developing a full feature.

bug-create — Command by Pimzino

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/pimzino/claude-code-spec-workflow/bug-create

Clone the repo

git clone --depth 1 https://github.com/Pimzino/claude-code-spec-workflow

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

When invoked 680 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.00000	$0.00680
Opus 5	$0.00000	$0.00340
Sonnet 5	$0.00000	$0.00136
Haiku 4.5	$0.00000	$0.00068

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

Security

Grade A, and why

bug-create 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 2d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

bug-create — 100% identical, 0 lines differ

src/markdown/commands/bug-create.md · 92 lines

How it starts

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

Bug Create Command

Initialize a new bug fix workflow for tracking and resolving bugs.

Usage

/bug-create <bug-name> [description]

Workflow Overview

This is the streamlined bug fix workflow - a lighter alternative to the full spec workflow for addressing bugs and issues.

Bug Fix Phases

Report Phase (This command) - Document the bug
Analysis Phase (/bug-analyze) - Investigate root cause
Fix Phase (/bug-fix) - Implement solution
Verification Phase (/bug-verify) - Confirm resolution

Instructions

You are helping create a new bug fix workflow. This is designed for smaller fixes that don't need the full spec workflow overhead.

Create Directory Structure
- Create .claude/bugs/{bug-name}/ directory
- Initialize report.md, analysis.md, and verification.md files

Load ALL Context Once (Hierarchical Context Loading) Load complete context at the beginning for the bug creation process:

# Load steering documents (if available)
claude-code-spec-workflow get-steering-context

# Load bug templates
claude-code-spec-workflow get-template-context bug

Gather Bug Information
- Take the bug name and optional description
- Guide user through bug report creation
- Use structured format for consistency
Generate Bug Report
- Template to Follow: Use the bug report template from the pre-loaded context above (do not reload)
- Create detailed bug description following the bug report template structure

Template Usage

Follow exact structure: Use loaded bug report template precisely
Include all sections: Don't omit any required template sections
Structured format: Follow the template's format for consistency

Request User Input
- Ask for bug details if not provided in description
- Guide through each section of the bug report
- Ensure all required information is captured
Save and Proceed
- Save the completed bug report to report.md
- Ask: "Is this bug report accurate? If so, we can move on to the analysis."
- Wait for explicit approval before proceeding

Read the full file on GitHub · 92 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.

2d ago First seen · 92 lines · 0 tokens per session scan A d757c6b98b41

Subscribe to this mod's changes

bug-create is a command published in the GitHub repository Pimzino/claude-code-spec-workflow (3,855 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 680 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.

Debugging Planning

bug-create

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

Bug Create Command

Usage

Workflow Overview

Bug Fix Phases

Instructions

Template Usage

What this file has done since we first saw it

Other commands, from other repositories

git

checklist

clarify

specify

analyze

constitution