request-refactor-plan

Interview users to create a tiny-commit refactor plan filed as a GitHub issue.

Updated May 7, 2026
One-click install
npx skills add https://github.com/hgxszhj/mattpocock_skills --skill request-refactor-plan-hgxszhj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: request-refactor-plan
Source: https://github.com/hgxszhj/mattpocock_skills/tree/main/skills/deprecated/request-refactor-plan
Command: npx skills add https://github.com/hgxszhj/mattpocock_skills --skill request-refactor-plan-hgxszhj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers create a structured, actionable plan for refactors by interviewing the user, mapping the current state, and outlining incremental commits. It then documents the plan as a GitHub issue to ensure alignment and traceability.

Core Features & Use Cases

  • Interview-driven scoping to capture requirements and constraints
  • Repository analysis to identify impact, risks, and test considerations
  • Tiny-commit plan and RFC drafting to enable safe incremental changes
  • GitHub issue creation to formalize the plan and track progress

Quick Start

Describe the refactor problem and desired outcomes in a single sentence to generate a tiny-commit plan and GitHub issue.

Frequently Asked Questions about request-refactor-plan

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

FAQPage Schema
How do I plan a codebase refactor into safe incremental steps?

Planning a codebase refactor involves interviewing the user, analyzing the repository for risks, and outlining tiny commits to ensure safe incremental changes. This approach breaks work into trackable steps to enable safe modifications.

What is the best way to draft an RFC for a repository refactor?

Drafting an RFC for a repository refactor uses interview-driven scoping to capture requirements, analyzes the codebase, and documents decisions. This creates a structured RFC with tiny-commit plans for safe incremental changes.

How do I file a refactor plan as a GitHub issue?

Filing a refactor plan as a GitHub issue requires generating an issue template from the tiny-commit plan. The system documents decisions and maps incremental changes into the issue to formalize alignment and track progress.

Does this refactor planning approach work for analyzing repository risks and test considerations?

Yes, this refactor planning approach conducts repository analysis to identify impact, risks, and test considerations. It maps the current state during the interview phase to ensure all technical constraints are captured.

Can I use this to break down large refactors across a team?

Yes, you can use this to break down large refactors across a team by outlining tiny commits and documenting decisions in a GitHub issue. This formalizes the plan to ensure team alignment and safe incremental execution.