domains / families / software-engineering / bug-fixing

bug-fixing

separate

Zero-regression bug fix workflow: triage → reproduce → root cause → impact analysis → fix → verify → knowledge deposit → self-reflect. Use when: - Feature broken, incorrect behavior, wrong output, errors/exceptions - Console errors/warnings even when feature appears functional - Regressions, timeouts, degraded performance - Keywords: "fix bug", "debug", "not working", "error", "broken" Output: Bug summary + verification report + code review + self-reflection score. Not for: new features (use fullstack-developer); pure review (use code-review); optimization (use performance-optimization).

When to use

• Feature broken
• Incorrect behavior
• Wrong output
• Errors or exceptions
• Console errors or warnings
• Regressions
• Timeouts
• Degraded performance

When not to use

• New features
• Pure review
• Optimization

Skill page

Source