Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nwave-ai/nw-refactor
Applies the Refactoring Priority Premise (RPP) levels L1-L6 for systematic code refactoring.
Passed 11 of 18 test cases with the skill, and 5 of 18 without it.
and 8 more in the full report
9 fixed5 passed either way7 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
If the test suite is RED after a batch edit on `src/checkout/`, what is the first diagnostic step before editing any files?
| Checked | Without skill | With skill |
|---|---|---|
| Diagnoses whether the breakage was caused by an unintended change to observable production behavior | Missed | Passed |
The instructions your model reads when the skill loads.
Wave: CROSS_WAVE
Agent: Crafty (nw-software-crafter)
Command: *refactor
Applies the Refactoring Priority Premise (RPP) — 6-level hierarchy L1 Readability|L2 Complexity|L3 Responsibilities|L4 Abstractions|L5 Design Patterns|L6 SOLID++. For complex multi-class refactorings, agent applies Mikado Method internally.
/nw-refactor runs batch-then-verify by default, regardless of test-suite speed:
Legacy incremental variant (opt-in only): the nw-progressive-refactoring skill documents the incremental L1→test→L2→test cycle. It is NOT the default — use it only when explicitly requested. Anchor: feedback_refactor_batch_when_test_suite_slow_2026_05_19 (the prior "only batch when suite slow" conditional is removed — batch is now unconditional).
@nw-software-crafter
Execute *refactor for {target-class-or-module}.
Context Files:
Configuration:
test cases passed, vs 5 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.