← ClaudeAtlas

bug-fixlisted

Bug fix workflow. Use when: fixing bugs, resolving issues, regression fixes. Not for: new features (use feature-dev), understanding code (use code-explore). Output: fix + regression test + review gate.
hmj1026/dhpk · ★ 1 · AI & Automation · score 77
Install: claude install-skill hmj1026/dhpk
# Bug Fix Skill ## Trigger - Keywords: bug, issue, fix, error, broken, failing ## When NOT to Use - New feature development (use feature-dev) - Just want to understand code (use code-explore) - Pure test-only tasks without feature changes (use `/codex-test-review` directly) ## Prohibited Actions ``` ❌ git add | git commit | git push — per @rules/execution-policy.md (Git pipeline) ``` This skill fixes bugs but does **not** commit. `/precommit` is a quality gate only. To commit, the user must invoke `/smart-commit --execute` separately. ## Workflow ``` Investigate → Locate → Fix → Test + Review → Precommit Gate │ │ │ │ │ ▼ ▼ ▼ ▼ ▼ gh issue Grep Edit /verify /precommit /git-investigate Read tests /codex-test-review /codex-review-fast ``` ## Phase 1: Investigation | Source | Action | |--------|--------| | GitHub Issue | `gh issue view <number>` | | Error message | `Grep("error message")` | | Code history | `/git-investigate` | **Output root cause analysis**: - Problem location: `src/<module>/<file>:<line>` - Root cause: <specific cause> - Impact scope: <which features are affected> ## Phase 2: Fix | Principle | Description | |-----------|-------------| | Minimal changes | Only modify what is necessary | | No new issues | Confirm changes don't affect other features | ## Phase 3: Add Regression Test ⚠️ Follow `@rules/testing.m