← ClaudeAtlas

bugfixlisted

Fix a bug the disciplined way, starting from a ticket. Use when asked to fix, debug, investigate, or resolve a bug, issue, or defect. Reads the ticket, reproduces the bug before touching code (by a test or script when possible, by guiding the author through manual steps when the bug involves a UI flow, an external service or generated output), keeps the steps, observations, evidence and hypotheses in the conversation so the fix is informed by what was seen, drives to the real root cause, fixes the cause and adds a regression test, verifies the repro no longer triggers and nothing else broke, then hands off to the pr skill or leaves its findings on the ticket. The ticket may be followed by what the author already knows about the bug; when it is not, the skill asks for it. Confirms the diagnosis with the author before changing any code.
sabind/ponderly · ★ 0 · Code & Development · score 72
Install: claude install-skill sabind/ponderly
# Fix a bug Fix a bug by driving from the ticket to a reproduction, then to the root cause, then to a fix that is guarded by a regression test. Confirm the diagnosis with the author before changing any code, and once the fix is verified hand off to the pr skill, or leave the findings on the ticket, as the author chooses. The author is accountable for the fix. The root cause and the fix must be understood, not guessed. A bug that merely stopped reproducing is not the same as a bug whose cause is known and prevented; do not treat "it works now" as a fix. Help the author understand the cause; do not assert one you cannot support from evidence. Argument, the ticket and anything the author already knows, or a description, if given: $ARGUMENTS ## Working with the author - **Stops.** The paste request in step 1, when the ticket cannot be read; the request for a missing symptom or expected behaviour in step 1, when there is no ticket; the approach question in step 2, when the advance context names no lead; the manual reproduction steps in step 3, when the bug cannot be reproduced by a test or script; the request for missing conditions and the author's choice to waive reproduction in step 3, when the bug cannot be reproduced; the root-cause confirmation in step 4; the manual re-run in step 6, after a manual reproduction; the hand-off question in step 7. - **How it asks.** With the AskUserQuestion tool, fixed options plus free text, at the approach question, the root-cause confirm