request-refactor-plan

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating a complex refactor is hard without a clear plan, visibility, and traceable progress. This Skill helps you discover the problem, define the scope, and produce a tiny-commit plan that can be filed as a GitHub issue.

Core Features & Use Cases

  • Interview-driven problem framing to capture the exact scope of the refactor.
  • Tiny-commit workflow that ensures incremental, testable changes.
  • Standardized GitHub issue templates to communicate decisions, scope, and testing strategy.
  • Use Case: When refactoring a legacy module, break changes into tiny, shippable commits and track progress with an issue.

Quick Start

Provide a detailed problem description and acceptance criteria to kick off a refactor plan.

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 code refactor with tiny commits?

To plan a code refactor with tiny commits, this Skill interviews you to define the scope and desired outcomes, then outlines an incremental, testable commit plan applied directly to your repository.

How do I create a GitHub issue for a refactoring plan?

You create a GitHub issue for a refactoring plan by generating a standardized template that includes the problem statement, proposed solution, tiny commits, decision document, testing decisions, and out-of-scope items.

What is the best way to define scope before refactoring a legacy module?

Defining scope before refactoring a legacy module is best handled through an interview-driven problem framing process that captures exact desired outcomes and establishes clear testing decisions before any code changes.

How do I track refactoring progress using GitHub issues?

You track refactoring progress using GitHub issues by applying a tiny-commit workflow that breaks complex changes into incremental steps, filing them as traceable issues with standardized decision documents.

What should be included in a refactoring issue template?

A refactoring issue template should include the problem statement, solution, tiny commits, decision document, testing decisions, out of scope items, and further notes to ensure full visibility and traceability.