do-refactor

Execute refactoring epics with sequential commits and CI verification.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/jamesc/skills --skill do-refactor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: do-refactor
Source: https://github.com/jamesc/skills/tree/main/skills/do-refactor
Command: npx skills add https://github.com/jamesc/skills --skill do-refactor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the execution of large refactoring tasks by breaking them down into sequential, verifiable commits on a dedicated branch, ensuring continuous integration and minimizing disruption.

Core Features & Use Cases

  • Sequential Issue Implementation: Executes child issues of a refactoring epic one by one.
  • CI Verification: Runs Continuous Integration checks after each commit to ensure code stability.
  • Incremental PR Updates: Creates and updates a single Pull Request for the entire epic.
  • Use Case: When a large refactoring epic (e.g., BT-123) needs to be applied to the codebase, this skill will branch off main, implement each sub-task as a commit, verify CI, and update a single PR until the entire epic is complete.

Quick Start

Use the do-refactor skill to execute the refactoring epic BT-123.

Frequently Asked Questions about do-refactor

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

FAQPage Schema
How do I automate a large refactoring epic across multiple sequential commits?

To automate a refactoring epic, this Skill branches off main and implements child issues sequentially as individual commits. It handles dependency ordering and updates a single Pull Request incrementally until the entire epic is complete.

How does continuous integration verification work after each refactoring commit?

Continuous integration verification runs automatically after each child issue commit to ensure code stability. If CI checks fail, the Skill provides graceful failure recovery to prevent disrupting the overall refactoring epic execution.

Can I execute a refactoring epic on a single dedicated Git branch?

Yes, you can execute a refactoring epic on a single dedicated Git branch. This approach minimizes disruption to other development work by isolating all sequential child issue implementations and CI verifications on one branch.

What is the best way to handle dependency ordering when implementing child issues?

The best way to handle dependency ordering is using automated prerequisite validation. The Skill evaluates child issue dependencies before execution, ensuring sequential implementation maintains behavioral preservation and correct commit ordering.

Why use a single Pull Request for an entire refactoring epic instead of multiple PRs?

Using a single Pull Request for a refactoring epic minimizes disruption and ensures behavioral preservation. The Skill creates and incrementally updates one PR, providing a unified view of all sequential commits and CI verification results.

What happens if CI verification fails during a sequential refactoring commit?

If CI verification fails during sequential refactoring, the Skill initiates graceful failure recovery. This prevents incomplete commits from breaking the dedicated branch while preserving the already verified child issue implementations.