request-refactor-plan

Create detailed refactor plans and file them as GitHub issues.

1|Updated May 25, 2026
One-click install
npx skills add https://github.com/chiruu12/nudge --skill request-refactor-plan-chiruu12
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: request-refactor-plan
Source: https://github.com/chiruu12/nudge/tree/main/.agents/skills/request-refactor-plan
Command: npx skills add https://github.com/chiruu12/nudge --skill request-refactor-plan-chiruu12

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of creating a safe and effective refactor plan, ensuring that code refactoring is done without introducing new bugs or issues.

Core Features & Use Cases

  • Structured Interviews: Guides users through a detailed interview process to understand the problem and potential solutions.
  • GitHub Issue Creation: Automates the creation of a GitHub issue with a comprehensive refactor plan, including problem statements, solutions, commit plans, and decision documents.
  • Use Case: When a developer is tasked with refactoring a complex part of the codebase and needs a structured plan to ensure the refactor goes smoothly.

Quick Start

Use the request-refactor-plan skill to start planning a refactor for the 'user-management' 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 code refactoring plan that keeps the codebase working at every step?

A structured code refactoring plan guides you through problem descriptions, alternatives, test coverage, and commit plans. This ensures each step leaves the codebase in a working state and is independently reviewable, preventing new bugs during complex module updates.

Can I automatically create a GitHub issue for my code refactoring plan?

Yes, you can automate GitHub issue creation for your refactor plan. The generated issue includes problem statements, proposed solutions, commit plans, and decision documents, ensuring your development workflow tracks the refactoring safely and precisely.

What is the best way to document problem statements and alternatives before refactoring?

The best way to document problem statements and alternatives is through a structured interview process. This captures the necessary context for safe refactoring and generates decision documents to guide future code review and development workflow.

Does this structured refactoring approach work for complex module updates?

Yes, structured refactoring is designed for complex codebase modules. By handling problem descriptions, test coverage, and structured commit plans, the workflow ensures the refactor goes smoothly without introducing new issues into the codebase.

How do I structure commit plans for a code refactor to ensure independent reviewability?

Structure commit plans by breaking down the refactoring into steps where each step leaves the codebase in a working state. This ensures every commit is independently reviewable and aligns with the overall issue tracking workflow.