52-execute-refactor-150

Coordinate a three-stage refactoring workflow with research, planning, implementation, and cleanup.

Updated Jan 30, 2025
One-click install
npx skills add https://github.com/MykhailoDmytriakha/my-preacher-helper --skill 52-execute-refactor-150
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 52-execute-refactor-150
Source: https://github.com/MykhailoDmytriakha/my-preacher-helper/tree/main/.codex/skills/52-execute-refactor-150
Command: npx skills add https://github.com/MykhailoDmytriakha/my-preacher-helper --skill 52-execute-refactor-150

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates a safe, end-to-end refactor workflow by guiding researchers, planners, and implementers through staged activities and clear decision points, reducing risk and uncertainty.

Core Features & Use Cases

  • Stage 1: Research refactor options with an investigation log to capture findings and sources.
  • Stage 2: Plan, confirm, implement with tests and validations, and document risks and edge cases.
  • Stage 3: Scout105 cleanup protocol to apply objective, minimal changes after milestones, with user approval.
  • Use Case: When asked to refactor a module to improve modularity and reduce duplication, you can follow the three-stage process and ensure tests pass before changes reach production.

Quick Start

Initiate Stage 1 by starting an investigations log and generating initial refactor options, then progress through staged planning, implementation, and cleanup with validation.

Frequently Asked Questions about 52-execute-refactor-150

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

FAQPage Schema
How do I safely coordinate a large codebase refactor?

Safely coordinate codebase refactoring by using a three-stage workflow: research options, plan and implement with tests, then apply cleanup with approval gating. This staged process reduces risk and uncertainty for significant code restructuring.

What is the best way to plan a staged code modularization?

The best way to plan staged code modularization is through a structured workflow covering research, planning, implementation, and cleanup. Stage 1 captures findings in an investigation log, Stage 2 implements with tests, and Stage 3 handles objective cleanup.

How do I validate code changes during a major restructuring?

Validate code changes during major restructuring by applying stage-by-stage validation and tests. Stage 2 requires confirming that tests pass and documenting risks and edge cases before changes reach production, ensuring safe codebase modifications.

Can I apply cleanup changes automatically after a milestone?

You cannot apply cleanup changes automatically; Stage 3 uses a cleanup protocol to apply objective, minimal changes after milestones, but it requires explicit user approval gating before any cleanup modifications are executed.

When do I need an investigation log for refactoring?

You need an investigation log for refactoring during Stage 1 to capture research findings and sources for refactor options. It provides a structured record of investigations to guide subsequent planning and implementation decisions.

Does this refactoring workflow require any external dependencies?

This refactoring workflow does not require external dependencies. It is a self-contained process that guides researchers, planners, and implementers through staged activities and decision points using an investigation log template and defined exit criteria.