skills.rest
paialex
paialexCOMMUNITY
Explore all skills by this author →
GitHub

request-refactor-plan

Interview stakeholders and draft a refactor plan with incremental commits.

1|Updated Feb 13, 2026
Search Tags:#planning#commit#codebase#github#interview#refactor
One-click install
npx skills add https://github.com/paialex/ai-skills-bank --skill request-refactor-plan-paialex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: request-refactor-plan
Source: https://github.com/paialex/ai-skills-bank/tree/main/mattpocock_skills/deprecated/request-refactor-plan
Command: npx skills add https://github.com/paialex/ai-skills-bank --skill request-refactor-plan-paialex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams plan safe, incremental refactors by turning a vague problem into a concrete, commit-by-commit plan and an actionable GitHub issue.

Core Features & Use Cases

  • Interview-driven scoping: Collects the problem, constraints, and goals from stakeholders to define the refactor scope.
  • Incremental plan: Breaks the work into tiny, testable commits with clear success criteria.
  • RFC generation: Creates a formal GitHub issue describing the refactor approach, decisions, and acceptance criteria.

Quick Start

Initiate a detailed interview to outline the problem and generate a plan of tiny commits.

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 safe codebase refactor with incremental commits?▼

Planning a safe codebase refactor involves interviewing stakeholders to document the problem, validating the current codebase, exploring options, and drafting an RFC with incremental commits to ensure safe transitions.

What is the best way to document a refactor plan for a GitHub issue?▼

Documenting a refactor plan for a GitHub issue requires generating a formal RFC that outlines the approach, captures stakeholder decisions, specifies test plans, and lists acceptance criteria for the codebase changes.

How do I scope a codebase refactoring project using stakeholder interviews?▼

Scoping a refactoring project via stakeholder interviews involves collecting the problem, constraints, and goals to define the exact refactor scope and validate the current codebase before exploring technical options.

Does this refactor planning approach work for large legacy codebases?▼

Yes, this refactor planning approach works for large legacy codebases by breaking down massive changes into tiny, testable commits, with interview-driven scoping ensuring all constraints are documented before any code is modified.

Why should I break a refactor into tiny commits instead of one large pull request?▼

Breaking a refactor into tiny commits ensures each change is testable and safe, reducing the risk of introducing bugs while allowing stakeholders to validate incremental progress against clear success criteria.

What limitations exist when generating an RFC for a codebase refactor?▼

A limitation of generating an RFC for a codebase refactor is that it relies entirely on accurate stakeholder input during the interview process; incomplete problem documentation will yield a GitHub issue lacking actionable test plans.

Related Skills

Explore More Software Engineering Skills→
githubgithub
37.6k

make-repo-contribution

Guide contributors through repository issue, branch, commit, and pull request guidelines.

Official
Basic
InditexTechInditexTech
195

request-refactor-plan

Convert vague refactor ideas into incremental plans and GitHub issues.

Official
Advanced
gooftroopgooftroop

mastering-github-cli

Search GitHub repositories, monitor CI/CD pipelines, and manage Actions workflows via CLI.

Community
Advanced
CarGDevCarGDev

Code Auditor

Audit code quality by detecting dead code, complexity, duplication, and architectural smells.

Community
Intermediate