nw-progressive-refactoring

Refactor codebases progressively from readability to architecture using the Refactoring Priority Premise.

Updated Mar 18, 2024
One-click install
npx skills add https://github.com/v1bh0r/precise-ledger-pro --skill nw-progressive-refactoring-v1bh0r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nw-progressive-refactoring
Source: https://github.com/v1bh0r/precise-ledger-pro/tree/main/nWave/skills/nw-progressive-refactoring
Command: npx skills add https://github.com/v1bh0r/precise-ledger-pro --skill nw-progressive-refactoring-v1bh0r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Progressive refactoring framework that guides teams through a structured ladder of improvements, from readability to architectural refinement.

Core Features & Use Cases

  • RPP-based Level progression (L1 to L6) with mandatory sequencing.
  • 22 code smell taxonomy and atomic transformations for safe, incremental changes.
  • Clear guardrails and guidelines for maintaining test smells and project health.

Quick Start

Begin with Level 1 readability improvements before advancing to higher levels to steadily improve code quality.

Frequently Asked Questions about nw-progressive-refactoring

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 maintainability?

The Refactoring Priority Premise (RPP) is a progressive framework that improves maintainability by enforcing a mandatory cascade through six levels, focusing on readability before architectural changes to ensure safe, incremental codebase transformations.

How do I systematically refactor a legacy codebase to reduce code smells?

To systematically refactor legacy code, apply the RPP ladder starting with Level 1 readability improvements, utilizing a catalog of 22 code smells and atomic transformations to execute safe, incremental changes before advancing to higher architectural levels.

When should I prioritize code readability over architectural refactoring?

Code readability must be prioritized before architectural refactoring because the progressive framework enforces a mandatory sequence, requiring you to complete Level 1 readability improvements before advancing to higher levels for architectural refinement.

What is the best way to structure incremental code refactoring across multiple levels?

The best way to structure incremental refactoring is using a multi-level hierarchy from L1 to L6, applying atomic transformations and clear guidelines to steadily improve code quality while maintaining test smells and project health.

Does progressive refactoring require specific dependencies or components to work?

Progressive refactoring does not require specific dependencies or components, allowing you to apply the RPP-based level progression and 22 code smell taxonomy directly to your existing codebases without external tool integrations.

Why does my code refactoring keep breaking existing project health and test smells?

Code refactoring breaks project health when bypassing the mandatory L1 to L6 cascade, but you can prevent this by following clear guardrails and practical guidelines for safe, incremental changes that maintain test smells during transformations.