request-refactor-plan

Plan GitHub pull requests with refactor strategies and test plans.

Updated Feb 28, 2019
One-click install
npx skills add https://github.com/rjschie/dotfiles --skill request-refactor-plan-rjschie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: request-refactor-plan
Source: https://github.com/rjschie/dotfiles/tree/main/files/claude/skills/request-refactor-plan
Command: npx skills add https://github.com/rjschie/dotfiles --skill request-refactor-plan-rjschie

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the need for a systematic approach to planning and documenting code refactorings, facilitating cleaner, maintainable codebases and efficient collaborative processes.

Core Features & Use Cases

  • Problem Solving Interview: Gathers detailed problem statements and solution ideas through user interviews.
  • Code Analysis: Evaluates current codebase conditions to ensure refactor assumptions are sound.
  • Options and Decisions: Explores alternative approaches and defines the refactor's scope and inclusions/exclusions.
  • Test Coverage Assessment: Evaluates test coverage and testing strategies.
  • Refactoring Plan Documentation: Breaks down refactorings into actionable steps, with testable results, in a GitHub issue.

Quick Start

Create a refactor plan for 'issue-1234', detailing the changes required to optimize the payment processing flow.

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 for a GitHub pull request?

To create a code refactoring plan for a GitHub pull request, this Skill conducts a problem-solving interview, analyzes the codebase, and documents actionable steps with test plans directly in a GitHub issue.

What is the best way to document technical refactoring strategies for a Python environment?

The best way to document technical refactoring strategies is to define problem statements, explore alternative options, and detail test coverage assessments in a structured GitHub issue for Python environments.

Does this GitHub refactoring workflow support defining inclusions and exclusions for codebase changes?

Yes, this GitHub refactoring workflow explicitly supports defining inclusions and exclusions, allowing you to set clear scope boundaries and document non-inclusions within the generated refactoring strategy.

Can I assess test coverage strategies when planning code refactoring tasks?

Yes, you can assess test coverage strategies when planning code refactoring tasks, as the workflow evaluates current testing conditions to ensure refactor assumptions are sound before issuing the pull request.

Do I need Git tools to generate a refactoring plan issue on GitHub?

Yes, you need Git tools and a Python environment to generate a refactoring plan issue on GitHub, as the Skill assumes these dependencies are present for analyzing codebase conditions and collaborating on the platform.

Why should I use a structured issue template for software refactoring instead of ad-hoc documentation?

Using a structured issue template for software refactoring ensures systematic documentation of problem definitions and implementation details, facilitating cleaner codebases and more efficient collaborative processes than ad-hoc documentation.