request-refactor-plan

To create a refactoring plan and track it, this Skill conducts an interactive interview to explore your codebase, breaks down the changes into tiny commits, and files the detailed plan directly as a GitHub issue.

The best way to break down a large codebase refactor is through an interview-based planning process that assesses alternative solutions, details testing coverage, and divides the implementation into a sequence of tiny commits.

To ensure testing coverage during code refactoring, the planning process includes a specific testing coverage analysis phase to verify robust testing strategies are in place before filing the GitHub issue.

Yes, you need GitHub access to generate and track a refactor plan because the Skill requires user interaction during the interview and relies on GitHub integration to file the final refactor plan as an issue.

Yes, you can assess alternative solutions before committing because the planning workflow explicitly presents options, evaluates different refactoring approaches, and incorporates your feedback before finalizing the implementation details.

An interview-based process for software refactoring verifies your assertions against the actual codebase state, ensuring the generated plan is accurate and comprehensive rather than relying on manual assumptions.