nw-bugfix
Routes an observed defect through host-owned diagnosis and nwdes delivery artifacts.
Install / Use
npx skills add nWave-ai/nWave --skill nw-bugfixInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of nw-bugfix
nw-bugfix scores 84/100 on our quality scale, 2972nd of 4,702 Development & Engineering skills we index.
Its SKILL.md is 5.7 KB long, well organised into 13 sections with 6 code examples: a solid amount of guidance for an agent.
It has 617 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so nw-bugfix is actively maintained.
- Our last check on 2026-11-06 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-08. Automated pattern scan on 2026-10-08. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
nw-bugfix compared with similar skills
All 4 of these similar skills score higher than nw-bugfix; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| nw-bugfix (this skill)by nWave-ai | 84 | 617 | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.6k | 9d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.3k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.4k | 3d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.7k | today | MCP Server |
Frequently asked questions
- How do I install nw-bugfix?
- Run
npx skills add nWave-ai/nWave --skill nw-bugfix. The install tabs above show the steps for each supported agent. - Which AI agents does nw-bugfix work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is nw-bugfix safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is nw-bugfix still maintained?
- The repository was last updated about 2 months ago, so nw-bugfix is actively maintained.
Skill content
View source on GitHubname: nw-bugfix description: "Bug fix workflow: root cause analysis → user review → regression test + fix via TDD" user-invocable: true argument-hint: '[bug-description] - Describe the defect observed'
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
└─ /nw-deliver "fix-{bug-id}" — roadmap-based bugfix flow
└─ Paradigm detection determines crafter (OOP or FP)
└─ 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 methodologynw-investigation-techniques— systematic debugging patternsnw-post-mortem-framework— structured incident analysis
Invoke @nw-troubleshooter via Agent tool:
Execute *investigate-root-cause for the following defect:
{bug-description}
Configuration:
- investigation_depth: 5
- multi_causal: true
- evidence_required: true
Produce:
1. Root cause chain (5 Whys with evidence at each level)
2. Contributing factors
3. Proposed fix with specific code changes
4. Files affected
5. Risk assessment of the fix
After the troubleshooter returns, present findings to the user. Include:
- Root cause summary (1-2 sentences)
- Evidence chain
- Proposed fix
- Files to modify
- Risk level
STOP and wait for user confirmation before proceeding to Phase 3.
Phase 2: User Review
Present the RCA findings and ask:
- "Does this root cause match your understanding?"
- "Do you approve the proposed fix direction?"
- "Any additional constraints or context?"
If user rejects:
- Refine the RCA with additional context
- Or stop the workflow entirely
If user approves → proceed to Phase 3.
Phase 3: Regression Test + Fix
Phase 3 dispatches the fix through the roadmap-based bugfix flow. It does
paradigm detection (reads project CLAUDE.md for ## Development Paradigm),
crafter selection (@nw-software-crafter for OOP, @nw-functional-software-crafter
for FP), DES enforcement, and reads the rigor profile from
.nwave/des-config.json.
Preparation:
- Derive feature-id:
fix-{kebab-case-bug-summary}(max 5 words) - Create
docs/feature/{feature-id}/deliver/directory - Prepare RCA context from Phase 1 output (root cause, files affected, proposed fix)
Delegate to /nw-deliver:
/nw-deliver "fix-{bug-summary}"
The deliver orchestrator builds a minimal two-step roadmap:
Step 01-01: Regression test (RED)
- Write a test that reproduces the exact defect
- Test MUST fail against current code (proves the bug exists)
- Test location:
tests/regression/{component}/ortests/bugs/ - Test name:
test_bug_{description}.py
Step 01-02: Fix implementation (GREEN)
- Implement the minimal fix identified in RCA
- Run ALL tests — regression test must now PASS
- Existing tests must not regress
The crafter handles the TDD cycle (3-phase canon RED → GREEN → COMMIT per ADR-025) with DES monitoring.
Success Criteria
- [ ] Root cause identified with evidence at each causal level
- [ ] User reviewed and approved fix direction
- [ ] Regression test written that fails with the bug
- [ ] Fix implemented that makes the regression test pass
- [ ] All existing tests still pass (no regressions)
- [ ] Commit with conventional message:
fix(scope): description
Examples
Example 1: Runtime crash
/nw-bugfix "DES hook crashes with FileNotFoundError when template schema is missing"
Phase 1: Rex traces to missing step-tdd-cycle-schema.json in plugin cache.
Phase 2: User confirms.
Phase 3: /nw-deliver "fix-missing-template-schema" → crafter writes test_bug_missing_template_schema.py (RED), adds fallback path resolution (GREEN), commits.
Example 2: Silent failure
/nw-bugfix "Skills plugin reports success but installs zero files when source has nw-prefixed layout"
Phase 1: Rex traces to is_public_skill() returning False for all nw-prefixed names due to ownership map key mismatch.
Phase 2: User confirms.
Phase 3: /nw-deliver "fix-ownership-map-keys" → crafter writes regression test with nw-prefixed fixture (RED), fixes ownership map keys (GREEN), commits.
Example 3: Functional project bug
/nw-bugfix "Pipeline composition breaks when filter predicate returns None"
Phase 1: Rex traces to missing None guard in compose() function.
Phase 2: User confirms.
Phase 3: /nw-deliver "fix-compose-none-guard" → paradigm detected as FP → @nw-functional-software-crafter writes property-based test (RED), adds None guard (GREEN), commits.
Notes
- This command is for known defects (something is broken). For new features, use
/nw-deliver. - The regression test is the primary deliverable — it prevents the bug from recurring.
- Keep the fix minimal. Refactoring belongs in
/nw-refactor, not here. - If the RCA reveals a design flaw (not just a code bug), escalate to
/nw-designbefore fixing. - Phase 3 delegates to
/nw-deliver, which handles paradigm detection, DES enforcement, and rigor profile automatically.
Related Skills
taste-skill
117.6kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.3kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.4kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.7k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
