Verified:GitHub

refactor-plan

Generates a phased multi-file refactoring plan with verification and rollback steps.

1|1|Updated Jan 29, 2026

Search Tags:#planning #software engineering #checklist #refactoring #rollback #dependency analysis #code migration

One-click install

npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill refactor-plan-ultraviollettnympho

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: refactor-plan
Source: https://github.com/ultraviollettnympho/transit-ticket/tree/main/.github/skills/refactor-plan
Command: npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill refactor-plan-ultraviollettnympho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multi-file refactors often fail because changes are made in the wrong order, dependencies are missed, or there is no way to recover when something breaks. This Skill turns a refactoring goal into a structured, sequenced execution plan before any code is touched. ## Core Features & Use Cases - Dependency-Aware Sequencing: Orders changes safely across phases: types and interfaces first, then implementations, then tests, then cleanup. - Verification Checkpoints: Every step includes an explicit check (such as running npm test) to confirm the change worked before proceeding. - Rollback Planning: Produces undo steps and a risk list so a failed refactor can be reverted cleanly. - Use Case: You need to rename a core data model used across 20 files. Invoke this Skill to get an affected-files table, a phased checklist, and a rollback plan before editing anything. ## Quick Start Ask the AI to create a refactor plan for your change, for example: plan a refactor to migrate the authentication module from callbacks to async/await.

Frequently Asked Questions about refactor-plan

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

FAQPage Schema

How do I plan a large multi-file refactor safely?▼

Start by mapping all affected files and their dependencies, then sequence changes so types and interfaces land before implementations and tests. This Skill generates that plan as a phased checklist with verification steps after each change.

What order should refactoring changes be made in?▼

Change types and interfaces first, then update implementations, then update tests, and finally remove deprecated code. This ordering keeps the codebase compilable between steps and makes failures easier to isolate.

How do I roll back a failed refactor?▼

Define rollback steps before starting, ideally one undo action per execution phase. The plan this Skill produces includes a dedicated rollback section so each phase can be reverted if verification fails.

When should I not use a formal refactor plan?▼

Skip the formal plan for single-file, low-risk edits like renaming a local variable or fixing a typo. The phased planning overhead only pays off when changes span multiple files with interdependencies.