skills.rest
mnadalc
mnadalcCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

request-refactor-plan

Generate a refactoring plan and create a GitHub issue with commit breakdown.

Updated Aug 27, 2026
Search Tags:#planning#code review#refactoring#software development#github issues#commit strategy
One-click install
npx skills add https://github.com/mnadalc/dotfiles --skill request-refactor-plan-mnadalc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: request-refactor-plan
Source: https://github.com/mnadalc/dotfiles/tree/main/.ai/skills/request-refactor-plan
Command: npx skills add https://github.com/mnadalc/dotfiles --skill request-refactor-plan-mnadalc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill helps users create detailed refactoring plans for software projects, breaking down complex changes into manageable steps.

Core Features & Use Cases

  • Problem Definition: Captures the user's problem statement and proposed solutions.
  • Codebase Exploration: Verifies assertions and understands the current state of the codebase.
  • Option Analysis: Explores alternative solutions and discusses implementation details.
  • Test Coverage Assessment: Checks for and addresses insufficient test coverage.
  • Commit Planning: Breaks down the implementation into granular, testable commits.
  • GitHub Issue Creation: Generates a comprehensive GitHub issue with a refactor plan.

Quick Start

Use the request-refactor-plan skill to generate a refactoring plan for the user authentication module.

Frequently Asked Questions about request-refactor-plan

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

FAQPage Schema
How do I create a refactoring plan for a complex software module?▼

A refactoring plan breaks down complex code changes into manageable steps by defining the problem, exploring the codebase, and planning granular commits. It provides a structured implementation strategy with clear testing decisions and out-of-scope items.

What is the best way to break down a large code refactoring task into commits?▼

Breaking down a refactoring task involves assessing test coverage, discussing implementation details, and sequencing the work into small, testable commits. This approach ensures each step is verifiable and minimizes regression risk.

How do I document a refactoring strategy for a GitHub issue?▼

Documenting a refactoring strategy in a GitHub issue involves outlining the problem statement, proposed solution, commit breakdown, and testing decisions. It generates a comprehensive decision document for team collaboration and progress tracking.

Can I generate a commit strategy for code review before implementing changes?▼

Yes, you can generate a commit strategy for code review by analyzing the codebase and planning implementation details beforehand. This produces a granular commit breakdown that guides the actual development and review process.

How do I assess test coverage when planning a code refactoring project?▼

Assessing test coverage during a refactoring project involves exploring the codebase to verify existing tests and addressing insufficient coverage. This ensures the refactored code remains stable and functional throughout the transition.

Related Skills

Explore More Software Engineering Skills→
BerryKuipersBerryKuipers
7

record-quality-baseline

Record code quality metrics before refactoring into a timestamped JSON baseline.

Community
Intermediate
connectwithprakashconnectwithprakash

GitHub Issue Fixer

Fix GitHub issues end-to-end from exploration to linked pull request creation.

Community
Advanced
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate
0xDarkMatter0xDarkMatter
29

structural-search

Search codebases by AST patterns using ast-grep and Bash.

Community
Intermediate