SKILL.md
Bug Issue
Use this skill to fix bugs or regressions reported in a GitHub issue.
How this differs from feature-issue
- Focuses on reproducing and diagnosing a problem, not building new functionality.
- Requires a root-cause analysis and regression tests.
Workflow
- Issue analysis
- Require an issue number argument. If missing, ask for it. - gh issue view <issue-number> - Summarize expected vs actual behavior. - If anything is unclear, interview the user for clarification and reproduction details.
- Reproduce
- Follow the steps from the issue. - If you cannot reproduce, ask for logs, environment details, or a minimal repro.
- Root cause
- Identify the smallest code path that triggers the issue. - Explain the cause in one paragraph before coding the fix.
- Fix
- Implement the minimal change that addresses the root cause. - Keep changes tightly scoped.
- Tests and validation
- Add or update tests to prevent regression. - Run relevant checks and fix diagnostics before proceeding.
- Review-first checkpoint
- Summarize changes, root cause, and test results. - Do not start a commit. The user initiates the commit process when ready.