nw-bugfix

Featured

Bug fix workflow: root cause analysis → user review → regression test + fix via TDD

AI & Automation 636 stars 68 forks Updated today MIT

Install

View on GitHub

Quality Score: 95/100

Stars 20%
93
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# NW-BUGFIX: Defect Resolution Workflow **Wave**: CROSS_WAVE **Agents**: Rex (nw-troubleshooter) → selected crafter (OOP or FP per project paradigm) ## Overview End-to-end bug fix pipeline: diagnose root cause, review findings with user, then deliver regression tests that fail with the bug and pass with the fix. Ensures every defect produces a test that prevents recurrence. ## Flow ``` INPUT: "{bug-description}" │ ├─ Phase 1: Root Cause Analysis (@nw-troubleshooter) │ └─ /nw-root-why "{bug-description}" │ └─ Output: RCA document with root cause chain + fix proposal │ ├─ Phase 2: User Review (INTERACTIVE — STOP here) │ └─ Present RCA findings to user │ └─ User confirms root cause + approves fix direction │ └─ If user rejects → refine RCA or stop │ └─ Phase 3: Regression Test + Fix (via /nw-deliver) └─ /nw-deliver "fix-{bug-id}" with bug-fix scope └─ Paradigm detection determines crafter (OOP or FP) └─ Roadmap: regression test (RED) → fix (GREEN) → verify (COMMIT) ``` ## Execution Steps ### Phase 1: Root Cause Analysis **Skill loading**: The troubleshooter loads its skills from `~/.claude/skills/nw-{skill}/SKILL.md`: - `nw-five-whys-methodology` — core investigation methodology - `nw-investigation-techniques` — systematic debugging patterns - `nw-post-mortem-framework` — structured incident analysis Invoke @nw-troubleshooter via Agent tool: ``` Execute *investigate-root-cause for the following defect: {bug-description...

Details

Author
nWave-ai
Repository
nWave-ai/nWave
Created
9 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category