⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
bug-fix
Bug-fixing workflow that coordinates diagnosis, test-driven reproduction, root-cause analysis, and targeted fixes. Use when the user wants to fix a bug with thorough investigation and regression testing.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
// README
claude-swe-workflows
A system of composable software engineering workflows for [Claude Code][cc]. Plan projects, implement tickets, and run quality passes — from a single ticket to a multi-batch project, using the same layered architecture.
Installation
claude plugin marketplace add https://github.com/chrisallenlane/claude-swe-workflows.git
claude plugin install claude-swe-workflows@claude-swe-workflows
Layered Composition
The skills are arranged as layered composition — higher-level skills invoke lower-level ones. Enter at the layer that matches your task. The deepest stack:
/lead-project ← autonomous tech lead (decides what to do next)
└── invokes any skill below
/implement-project ← full-lifecycle project execution
└── /implement-batch ← one batch of related tickets
└── /implement ← one ticket, end-to-end
└── SME agents ← language-specific specialists
Three other entry points orchestrate bounded autonomous loops:
/lead-bug-hunt— loops/bug-hunt→/implement-batchuntil bugs converge below a severity floor./lead-refactor—/refactor→ loops/review-arch+/implement-batch→/refactor./lead-review— runs every/review-*sub-skill once.
Planning feeds implementation: /scope-project → /implement-project, or
/scope → /implement. Supporting skills (/think-*, /review-*, /bug-*,
/tidy-*) compose into any of the orchestrators above or run standalone.
Namespaces
Skills are grouped by namespace for discoverability. Each namespace gathers skills with a related purpose.
| Namespace | Purpose | Skills |
|---|---|---|
/lead-* | Autonomous orchestrators | /lead-project, /lead-bug-hunt, /lead-refactor, /lead-review |
/implement-* | Implement tickets (mutate the working tree) | /implement, /implement-batch, /implement-project |
/scope-* | Plan and produce tickets | /scope, /scope-project |
/review-* | Advisory audits — no code changes | /review-arch, /review-test, /review-perf, /review-a11y, /review-health, /review-security, /review-release |
/think-* | Reasoning support — no artifacts | /think-reframe, /think-brainstorm, /think-diagnose, /think-ach, /think-deliberate, /think-premortem, /think-scrutinize, /think-reflect |
/tidy-* | Mechanical hygiene | /tidy-docs, /tidy-git |
/bug-* | Find and fix bugs | /bug-fix, /bug-hunt |
/test-* | Test-quality work | /test-mutation |
| (standalone) | Skills that don't share a namespace | /refactor, /pre-compact, /release |
The /lead-* and /implement-* namespaces additionally share an autonomy
discipline (commander's intent, pre-loaded options, pre-rebutted
recommendations, risk budgets) — see
references/autonomy.md. The /think-* namespace
shares a design discipline (practitioner-sourced countermeasures to specific
cognitive failure modes) — see references/think.md.
Choosing a Workflow
Not everything needs the full pipeline. Enter at the level that matches your task:
| You want to... | Use |
|---|---|
| Drive a project to completion autonomously, deciding what to work on | /lead-project |
| Implement an entire multi-batch project autonomously | /implement-project |
| Implement a batch of related tickets | /implement-batch |
| Implement a single ticket or feature | /implement |
| Plan a multi-batch project with adversarial review | /scope-project |
| Plan a single feature and create a ticket | /scope |
| Fix a bug with diagnosis and root-cause analysis | /bug-fix |
| Proactively hunt for bugs before they're reported | /bug-hunt |
| Iterate hunt → fix until bugs converge below a severity floor (autonomous) | /lead-bug-hunt |
| Comprehensively refactor (tactical + architectural + tactical, autonomous) | /lead-refactor |
| Pressure-test a problem's framing before solving it | /think-reframe |
| Brainstorm approaches to a goal | /think-brainstorm |
| Reason about why a phenomenon is happening | /think-diagnose |
| Narrow among competing hypotheses against evidence | /think-ach |
| Make a hard decision with adversarial deliberation | /think-deliberate |
| Imagine how a plan could fail, or how a hypothetical catastrophe could hit a running system | /think-premortem |
| Scrutinize an idea or plan before committing to it | /think-scrutinize |
| Reflect on a completed experience to update beliefs | /think-reflect |
| Clean up code quality (DRY, dead code, naming) | /refactor |
| Rethink module boundaries and architecture | /review-arch |
| Survey the test suite and surface gaps as tickets | /review-test |
| Verify test quality via mutation testing | /test-mutation |
| Tidy all project documentation | /tidy-docs |
| Pre-release readiness check | /review-release |
| Cut a versioned release (preflight + plan + execute) | /release |
| Audit web content for accessibility barriers | /review-a11y |
| First-pass strategic orientation on a repo |
// HOW IT'S BUILT
KEY FILES