/nw-bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD
Claude Code
$ npx -y skills add nWave-ai/nWave --skill nw-bugfix --agent claude-code
Codex
$ npx skills add nWave-ai/nWave --skill nw-bugfix -a codex -y
Cursor
$ npx skills add nWave-ai/nWave --skill nw-bugfix -a cursor -y
Gemini CLI
$ npx skills add nWave-ai/nWave --skill nw-bugfix -a gemini-cli -y
GitHub Copilot
$ npx skills add nWave-ai/nWave --skill nw-bugfix -a github-copilot -y
OpenCode
$ npx skills add nWave-ai/nWave --skill nw-bugfix -a opencode -y
Windsurf
$ npx skills add nWave-ai/nWave --skill nw-bugfix -a windsurf -y
SKILL.md
nw-bugfix.SKILL.mdname: nw-bugfix
description: Routes an observed defect through host-owned diagnosis and nwdes delivery artifacts.
user-invocable: true
argument-hint: '<observed defect>'
NW-BUGFIX
Use this route when the root cause is not yet known. A defect whose root cause is established, found during current work, is fixed in place in the current lane instead: regression test observed RED, fix, GREEN, one commit, covered by that Request's review and CI (`nw-auto` recovery table). No separate Request.
Before authoring regression tests or changing code, load `nw-auto` and report the affected project's existing test baseline to the user as required by its visible-baseline rule. A broken setup is not the bug's intentional RED.
Use nwdes as the delivery route. Give the observed defect verbatim to the native installed Product Owner. Read `nw-nwdes` for the current route and `nw-role-invocation` for mandatory skills and exact role contracts. Generate instructions with `nwdes prompt`. Every role records through its kind's CLI verbs using Bash. The Product Owner records product values with `nwdes product` record edits and `nwdes product close`. The host writes no JSON and copies no reply into another command. For each role the route invokes, it passes that role's generated `nwdes prompt` bundle verbatim, and that role, not the host, runs its kind's verbs. Facts the route assigns to the host, such as `feature new` and `slice set`, stay with the host. Run every nwdes command from the checkout's top level; roots default to cwd and the repository root, and lane verbs resolve the main worktree. The first add, set or remove creates the scoped draft. Use `open --from-current` to revise current authority; close with no draft validates empty values.
Keep the defect verbatim in product authority and its matching public observation in acceptance authority. The architect records design values with design verbs. Before oracle authoring, generate the examiner's expectations prompt; it records expectations with `nwdes expectations row add/close`. The acceptance designer authors the regression oracle and records acceptance rows with `nwdes acceptance row add` for its assigned slice, then closes. The host runs its verification command on the original pre-fix source for RED. Never infer that source from HEAD after the fix is committed. The native crafter implements the correction and records changed files and command results with craft verbs for its assigned slice; the host captures GREEN.
After implementation, prepare actual public evidence with `nwdes packet --kind examine`. The examiner records each verdict with `nwdes examine verdict set` and closes with `nwdes examine close`. A fix no one observed working is not a fix. Invoke independent review separately; the reviewer records findings and closes its review with review verbs.
The LLM revises S/M/L, applicability, sequencing and upstream corrections from evidence. nwdes constructs artifacts, not code, models, workflow state or verification seals. `nw-auto` owns the common evidence and recovery guidance.
Read more
name: nw-bugfix description: Routes an observed defect through host-owned diagnosis and nwdes delivery artifacts. user-invocable: true argument-hint: '<observed defect>'
NW-BUGFIX
Use this route when the root cause is not yet known. A defect whose root cause is established, found during current work, is fixed in place in the current lane instead: regression test observed RED, fix, GREEN, one commit, covered by that Request's review and CI (`nw-auto` recovery table). No separate Request.
Before authoring regression tests or changing code, load `nw-auto` and report the affected project's existing test baseline to the user as required by its visible-baseline rule. A broken setup is not the bug's intentional RED.
Use nwdes as the delivery route. Give the observed defect verbatim to the native installed Product Owner. Read `nw-nwdes` for the current route and `nw-role-invocation` for mandatory skills and exact role contracts. Generate instructions with `nwdes prompt`. Every role records through its kind's CLI verbs using Bash. The Product Owner records product values with `nwdes product` record edits and `nwdes product close`. The host writes no JSON and copies no reply into another command. For each role the route invokes, it passes that role's generated `nwdes prompt` bundle verbatim, and that role, not the host, runs its kind's verbs. Facts the route assigns to the host, such as `feature new` and `slice set`, stay with the host. Run every nwdes command from the checkout's top level; roots default to cwd and the repository root, and lane verbs resolve the main worktree. The first add, set or remove creates the scoped draft. Use `open --from-current` to revise current authority; close with no draft validates empty values.
Keep the defect verbatim in product authority and its matching public observation in acceptance authority. The architect records design values with design verbs. Before oracle authoring, generate the examiner's expectations prompt; it records expectations with `nwdes expectations row add/close`. The acceptance designer authors the regression oracle and records acceptance rows with `nwdes acceptance row add` for its assigned slice, then closes. The host runs its verification command on the original pre-fix source for RED. Never infer that source from HEAD after the fix is committed. The native crafter implements the correction and records changed files and command results with craft verbs for its assigned slice; the host captures GREEN.
After implementation, prepare actual public evidence with `nwdes packet --kind examine`. The examiner records each verdict with `nwdes examine verdict set` and closes with `nwdes examine close`. A fix no one observed working is not a fix. Invoke independent review separately; the reviewer records findings and closes its review with review verbs.
The LLM revises S/M/L, applicability, sequencing and upstream corrections from evidence. nwdes constructs artifacts, not code, models, workflow state or verification seals. `nw-auto` owns the common evidence and recovery guidance.
AI agents that guide you from idea to working code, with human judgment at every gate. nWave runs inside Claude Code. It breaks feature delivery into seven waves (discover, diverge, discuss, design, devops, distill, deliver).
Other skills on nwave.
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about nw-bugfix.
- Which coding agents can use nw-bugfix?
- nw-bugfix installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

