skills.rest
jtucker9
jtucker9COMMUNITY
Explore all skills by this author →
GitHub

refactor-planner

Identify and prioritize refactor targets with risk scoring and staged PR roadmaps.

Updated Mar 13, 2026
Search Tags:#planning#roadmap#refactor#code-quality#risk-assessment#software-engineering#incremental-pr
One-click install
npx skills add https://github.com/jtucker9/mystuff --skill refactor-planner-jtucker9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: refactor-planner
Source: https://github.com/jtucker9/mystuff/tree/main/skills/development/refactor-planner
Command: npx skills add https://github.com/jtucker9/mystuff --skill refactor-planner-jtucker9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Refactor-planner helps engineering teams systematically identify, prioritize, and execute safe code refactors to improve maintainability and reduce debt.

Core Features & Use Cases

  • Identify targets: categorize smells, assess risk, and map impact.
  • Create incremental PR roadmaps: plan extraction steps, testing, and migration paths.
  • Generate before/after examples and regression tests to ensure behavior preserved.
  • Use case: phase out a god class by gradually extracting responsibilities into smaller, cohesive modules.

Quick Start

Provide a complete refactoring roadmap for a given codebase by identifying targets, assessing risk, and outlining incremental PR plans.

Frequently Asked Questions about refactor-planner

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

FAQPage Schema
What is incremental code refactoring and why plan it in stages?▼

Risk assessment scores refactor targets by analyzing file dependencies and existing test coverage. Files with high coupling and low test coverage receive higher risk scores, guiding the incremental PR roadmap to prioritize safer, lower-impact changes first.

How do I create an incremental PR roadmap to phase out a god class?▼

Refactor planning applies to mid-to-large software projects across multiple programming languages. It targets maintainability improvements by categorizing code smells and mapping dependencies regardless of the specific tech stack.

How does code smell discovery and risk scoring by files work?▼

Risk assessment scores refactor targets by analyzing file dependencies and existing test coverage. Files with high coupling and low test coverage receive higher risk scores, guiding the incremental PR roadmap to prioritize safer, lower-impact changes first.

Can I use incremental refactoring plans for mid-to-large software projects across languages?▼

Refactor planning applies to mid-to-large software projects across multiple programming languages. It targets maintainability improvements by categorizing code smells and mapping dependencies regardless of the specific tech stack.

What's the best way to ensure behavior is preserved during a module extraction?▼

The best way to preserve behavior is generating before/after examples and regression tests for each staged pull request. This verifies that the functional requirements remain satisfied as responsibilities are extracted into cohesive modules.

Related Skills

Explore More Software Engineering Skills→
SteveFeldmanSteveFeldman
5

code-review

Analyzes an entire software repository for architecture, security, performance, and testing issues.

Community
Advanced
lz-freedomlz-freedom

openspec-verify-change

Verify change artifacts for completeness, correctness, and coherence before archiving.

Community
Advanced
farmountainfarmountain
1

Refactor Agent

Detect code smells and apply incremental refactorings with test coverage.

Community
Advanced
devCharuzudevCharuzu

code-reviewer

Analyze pull requests for complexity, risk, and quality issues.

Community
Advanced