A structured process for fixing software bugs by reproducing the failure, finding its cause, applying a targeted change, and checking the result. A regression test is a test that helps ensure the bug does not return.

Use it to investigate errors, crashes, or unexpected behavior and to add tests that protect the corrected behavior.

It turns unclear bug reports into verifiable failures and reduces the chance that a fix creates another problem.

bug-fix — Skill for Claude Code by chrisallenlane

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.

Any agent

npx skills add chrisallenlane/claude-swe-workflows --skill bug-fix

Clone the repo

git clone --depth 1 https://github.com/chrisallenlane/claude-swe-workflows

Made for: Claude Code.

Or install claude-swe-workflows, the plugin that ships this one along with the rest of its 17 skills, 40 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/chrisallenlane/claude-swe-workflows/bug-fix/github.svg)](https://agentmods.dev/skills/chrisallenlane/claude-swe-workflows/bug-fix)

Your own site

<a href="https://agentmods.dev/skills/chrisallenlane/claude-swe-workflows/bug-fix"><img src="https://agentmods.dev/badge/skills/chrisallenlane/claude-swe-workflows/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/chrisallenlane/claude-swe-workflows/bug-fix"><img src="https://agentmods.dev/badge/skills/chrisallenlane/claude-swe-workflows/bug-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

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

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00041	$0.03666
Opus 5	$0.00020	$0.01833
Sonnet 5	$0.00008	$0.00733
Haiku 4.5	$0.00004	$0.00367

Measured 9d ago against content hash 812cab895176, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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 9d 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.

skills/bug-fix/SKILL.md · 395 lines

How it starts

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

Bugfix - Automated Bug-Fixing Workflow

Coordinates specialist agents through a bug-fixing cycle: clarify bug -> reproduce with failing test -> diagnose root cause -> implement fix -> verify -> review -> document.

Workflow

1. Clarify the bug

Gather bug details from user:

What are the symptoms? (error messages, unexpected behavior, crashes)
What is the expected behavior vs actual behavior?
How do you reproduce it? (steps, inputs, configuration)
When did it start? Any recent changes that might be related?
Environment specifics? (OS, versions, configuration)

Ask clarifying questions if needed:

Ambiguous symptoms
Missing reproduction steps
Unclear expected behavior

Loop back to user until the bug is clearly understood. You need enough information to write a test that demonstrates the failure.

2. Write Failing Test(s)

Detect project language/framework:

Check for language-specific files (go.mod, package.json, Cargo.toml, Dockerfile, Makefile, etc.)
Determine which specialist agent to use

Spawn appropriate SME agent:

If Golang project: spawn swe-sme-golang agent
If GraphQL schema/resolvers: spawn swe-sme-graphql agent
If Dockerfile changes: spawn swe-sme-docker agent
If Makefile changes: spawn swe-sme-makefile agent
If Ansible playbooks/roles: spawn swe-sme-ansible agent
If Zig project: spawn swe-sme-zig agent
If TypeScript project: spawn swe-sme-typescript agent
If JavaScript project: spawn swe-sme-javascript agent
If HTML/markup changes: spawn swe-sme-html agent
If CSS/styling changes: spawn swe-sme-css agent
Otherwise: write tests directly with general best practices

SME agent task:

Write test(s) that reproduce the reported bug
Tests should encode the expected behavior (so they fail against the current buggy behavior)
Run the tests and verify they actually fail
If the tests pass (bug cannot be reproduced): report back with findings — the bug may be environmental, already fixed, or misunderstood

Read the full file on GitHub · 395 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

references/README.md 20 KB

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.

9d ago First seen · 395 lines · 41 tokens per session scan A 812cab895176

Subscribe to this mod's changes

bug-fix is a skill published in the GitHub repository chrisallenlane/claude-swe-workflows (18 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 3,666 once invoked, about $0.0002 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 agentic-coding ai-agents ai-workflows anthropic automation claude

afc:issue

Analyze GitHub issue — investigate bug reports, understand requirements, inspect issues.

jhlee0409/all-for-claudecode · 19 tokens

afc:doctor

Diagnose afc plugin setup and health.

jhlee0409/all-for-claudecode · 13 tokens

afc:debug

Bug diagnosis and fix — root-cause analysis for errors, crashes, broken behavior.

jhlee0409/all-for-claudecode · 21 tokens

triage-issue

Analyze a GitHub issue, verify claims against the codebase, and close invalid issues with a technical response.

aden-hive/hive · 0 tokens

hive.error-recovery

Follow a structured recovery decision tree when tool calls fail instead of blindly retrying or giving up.

aden-hive/hive · 25 tokens

review-loop

Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…

sangrokjung/claude-forge · 100 tokens