nw-refactor

Refactor code across module, class, or project scopes using RPP levels L1-L6.

Updated Apr 15, 2026

Search Tags:#automation #refactoring #code-quality #software-engineering #rpp #mikado-method #modular-refactor

Ready to run

npx skills add https://github.com/StudentCristian/nWave-github --skill nw-refactor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: nw-refactor
Source: https://github.com/StudentCristian/nWave-github/tree/main/.github/skills/nw-refactor
Command: npx skills add https://github.com/StudentCristian/nWave-github --skill nw-refactor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically refactor code by applying the Refactoring Priority Premise (RPP) levels L1-L6 to produce progressive quality improvements across production and test code.

Core Features & Use Cases

Automated, staged refactoring passes aligned to RPP levels (L1 through L6)
Scope flexibility: operate at module, class, or project level with configurable level ranges and methods
Clear success criteria, planning options, and handoff deliverables for maintainable codebases

Quick Start

Run an automated refactor pass on the target codebase using the RPP levels from 1 through 6.

Frequently Asked Questions about nw-refactor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is the Refactoring Priority Premise and how does it improve code quality?▼

Automated code refactoring applies the Refactoring Priority Premise (RPP) method to systematically execute staged passes from L1 to L6. It progressively improves production and test codebases by operating across configurable module, class, or project boundaries.

How do I systematically refactor a large module without breaking existing tests?▼

To systematically refactor a module without breaking tests, apply the Refactoring Priority Premise (RPP) across staged levels L1 to L6. The process verifies success continuously against defined quality criteria and test results to ensure codebase stability.

Can I run automated refactoring passes on both production and test codebases?▼

Yes, automated refactoring using the Refactoring Priority Premise applies to both production and test codebases. You can configure the scope to target a specific class, an entire module, or the full project for progressive quality improvements.

What is the best way to plan staged refactoring for a software engineering project?▼

The best way to plan staged refactoring is using the Refactoring Priority Premise (RPP) framework, which offers configurable level ranges and refactor methods. It provides clear success criteria, planning options, and handoff deliverables for maintainable codebases.

Does modular refactoring support limiting the scope to a single class?▼

Yes, modular refactoring supports limiting the scope to a single class, a full module, or the entire project. You can configure specific level ranges and refactor methods to target exact boundaries within your production and test code.

When should I not use an automated L1 to L6 refactor method on my codebase?▼

You should not use an automated L1 to L6 refactor method when your codebase lacks defined quality criteria or comprehensive test results. The Refactoring Priority Premise process relies on verifying success at each stage, requiring existing tests to validate passes.