← ClaudeAtlas

bug-fixlisted

Diagnosis-first bug fixing with test-driven reproduction, root-cause analysis, and a targeted fix plus regression test. Use when the user wants to fix a bug with thorough investigation.
chrisallenlane/claude-swe-workflows · ★ 21 · AI & Automation · score 84
Install: claude install-skill chrisallenlane/claude-swe-workflows
# 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) **Spawn `swe-implementer` in reproduce-a-bug mode** (or write the tests directly when the bug is small and local). **Implementer 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 **This is the contract.** When these tests pass, the bug is fixed. **If reproduction fails:** - Return to step 1 for more information from the user - Report