cc-refactor

Coordinate end-to-end code refactoring planning and execution with risk-based approvals.

Updated May 7, 2026
One-click install
npx skills add https://github.com/lgzarturo/codeconductor --skill cc-refactor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cc-refactor
Source: https://github.com/lgzarturo/codeconductor/tree/main/.agents/skills/cc-refactor
Command: npx skills add https://github.com/lgzarturo/codeconductor --skill cc-refactor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams plan, justify, and safely execute large-scale code refactors with guardrails, required tests, and traceable steps.

Core Features & Use Cases

  • Architectural justification: generate a Refactor Plan with problem statement, target structure, affected files, and risk assessment.
  • Risk-guided execution: route through low, medium, or high-risk paths with appropriate approvals and change controls.
  • Verification and review: enforce pre/post-test runs, documentation, and code-review when needed to ensure behavior remains within plan.
  • Guardrails and documentation: clearly separate scope, out-of-scope work, and human-in-the-loop requirements to prevent scope creep.

Quick Start

Draft and obtain approval for a Refactor Plan, then execute the plan following the risk-guided routing and verification steps.

Frequently Asked Questions about cc-refactor

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

FAQPage Schema
How do I plan a large-scale code refactor safely?

Plan a code refactor safely by drafting a Refactor Plan that defines the problem statement, target structure, affected files, and risk assessment to establish guardrails and prevent scope creep before execution.

What is risk-based routing in code refactoring?

Risk-based routing in code refactoring directs execution through low, medium, or high-risk paths, applying appropriate human-in-the-loop approvals and change controls based on the assessed risk level of the affected modules.

How do I verify behavior remains unchanged after a software refactor?

Verify behavior remains unchanged after a software refactor by enforcing pre and post-test runs, requiring test coverage checks, and conducting a final code review to ensure implementation stays within the approved plan.

Can I use this for multi-file architectural refactoring across different modules?

Yes, this orchestrates end-to-end refactoring across modules with multiple files, coordinating architectural justification, risk-based routing, and human-in-the-loop approvals to manage complex structural changes.

What's the best way to prevent scope creep during code refactoring?

Prevent scope creep during code refactoring by enforcing guardrails that clearly separate in-scope and out-of-scope work, requiring documentation, and mandating human-in-the-loop approvals for any deviations from the Refactor Plan.