bugfixlisted
Install: claude install-skill xiongxianfei/rigorloop
# Structured bug fix workflow
You are fixing a defect, not just making a symptom disappear.
Use this skill when the task starts from unexpected behavior, a failing test, an incident, a regression, or a bug report.
## Inputs to read
Read, if present:
- bug report, issue, logs, screenshots, or failing test output;
- relevant spec and test spec;
- concrete plan if the bug belongs to active work;
- architecture docs or project map for affected flow;
- `AGENTS.md` and `CONSTITUTION.md`;
- related code and neighboring tests;
- recent changes that could have introduced the regression.
## Process
### 1. Understand expected behavior
State expected vs actual behavior.
If the expected behavior is not specified, identify the contract gap and decide whether to update or create a spec before fixing.
### 2. Reproduce
Find the smallest reliable reproduction:
- command;
- input;
- environment;
- data state;
- observed output or error.
If reproduction is not possible, collect evidence and explain uncertainty.
### 3. Diagnose root cause
Trace the path and classify the cause:
- spec gap;
- implementation error;
- integration mismatch;
- edge case;
- regression;
- data/migration issue;
- race/timing issue;
- configuration or environment issue;
- test bug.
Assess blast radius and look for the same pattern nearby.
### 4. Add regression test first
Before changing production code, add or update a test that fails because of the bug when feasible.
If not feasible, explain why and pr