skills.rest
pxlcrtiv
pxlcrtivCOMMUNITY
Explore all skills by this author →
GitHub

request-refactor-plan

Develop structured refactor plans through user interviews and incremental commits.

Updated Jul 3, 2026
Search Tags:#refactoring#codebase analysis#code planning#GitHub issues#incremental commits
One-click install
npx skills add https://github.com/pxlcrtiv/opencode-setup --skill request-refactor-plan-pxlcrtiv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: request-refactor-plan
Source: https://github.com/pxlcrtiv/opencode-setup/tree/main/skills/request-refactor-plan
Command: npx skills add https://github.com/pxlcrtiv/opencode-setup --skill request-refactor-plan-pxlcrtiv

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill assists in creating a detailed refactor plan with small, manageable commits, suitable for breaking down refactor requests into safe, incremental steps.

Core Features & Use Cases

  • User Interview: Guides the user through a structured interview process to understand the problem and potential solutions.
  • Codebase Analysis: Verifies user assertions and provides insights into the current code state.
  • Incremental Commits: Suggests breaking down the refactor into small, testable commits.
  • GitHub Issue Creation: Files the refactor plan as a GitHub issue with a detailed template.

Quick Start

Create a refactor plan for a code issue by running the skill with the issue reference.

Frequently Asked Questions about request-refactor-plan

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

FAQPage Schema
How do I break down a large codebase refactoring project into safe incremental commits?▼

To break down a codebase refactoring project, this Skill guides you through a structured interview to analyze your code and generate a plan with small, testable commits. It ensures each incremental step maintains test coverage for safe execution.

What is the best way to create an RFC for a codebase refactoring plan?▼

The best way to create an RFC for refactoring is using a structured interview process that verifies codebase assertions and translates them into actionable steps. This approach targets safe, incremental code changes formatted as a detailed GitHub issue.

Can I automatically file my refactoring plan as a GitHub issue?▼

Yes, you can file your refactoring plan as a GitHub issue. The Skill generates a detailed GitHub issue template containing the structured incremental commits and test coverage requirements gathered during the codebase analysis.

How does codebase analysis verify assertions during code planning?▼

Codebase analysis during code planning verifies your assertions by inspecting the current state of the code directly. This ensures that the generated refactoring steps are grounded in the actual codebase structure rather than assumptions.

Do I need existing test coverage to plan an incremental refactoring?▼

You do not need existing test coverage beforehand, but ensuring test coverage is a core part of the output. The generated refactoring plan explicitly includes test coverage requirements for each small, manageable commit to guarantee safe code changes.

Related Skills

Explore More Software Engineering Skills→
tonombtonomb

qa

Convert user-reported bugs into structured GitHub issues via guided QA sessions.

Community
Intermediate
leonanpereirapintoleonanpereirapinto
1

refactor

Refactor code safely by extracting methods and validating with tests.

Community
Intermediate
791994545791994545
4

to-issues

Convert plans, specifications, or PRDs into structured issues.

Community
Intermediate
0xrafasec0xrafasec
9

rfc

Create and review RFC markdown documents through structured interviews.

Community
Intermediate