Skip to content
Development
Command

/orch-refine-code

Orchestrate a behavior-preserving refactor — confirm tests green, restructure without changing behavior, keep green, review, gated commit. Wrapper for the orch-refine-code skill.

From plugin
ecc
239k109 skills72 agents109 commands7 hooks
+1
Install
> /plugin marketplace add affaan-m/ECC
> /plugin install ecc@ecc

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/orch-refine-code

Context preview

What this command does when you run it.

Orchestrate a behavior-preserving refactor — confirm tests green, restructure without changing behavior, keep green, review, gated commit. Wrapper for the orch-refine-code skill.

Command definition

orch-refine-code.md
description: Orchestrate a behavior-preserving refactor — confirm tests green, restructure without changing behavior, keep green, review, gated commit. Wrapper for the orch-refine-code skill.

/orch-refine-code

Manually launch the **orch-refine-code** orchestrator: improve structure while behavior stays identical, with the existing test suite as the safety net.

Usage

/orch-refine-code <what to restructure>

Examples:

/orch-refine-code extract the NWS HTTP client out of poller.py
/orch-refine-code remove dead code and duplication in the dashboard module

What It Does

Invoke the `orch-refine-code` skill with `$ARGUMENTS` as the request. The skill (via the shared `orch-pipeline` engine) will:

1. Classify size (default floor: standard — restructures touch multiple files). 2. Confirm the relevant tests exist and are **green before** touching code; add characterization tests first if coverage is thin. Plan the restructure. → **GATE 1**. 3. Restructure in small steps, re-running tests after each (no new behavior tests — the existing suite proves behavior is unchanged). Dead-code/dup sweeps delegate to `refactor-cleaner`. 4. `code-reviewer`, then commit as `refactor:` (the diff must be behavior-neutral). → **GATE 2**.

Use this only when behavior must **not** change. If behavior should change at all, use `/orch-change-feature` or `/orch-fix-defect`.

If `$ARGUMENTS` is empty, ask the user what to refine.

Read more
Ships withecc

Your agent can write code, but ECC gives it a coordinated engineering system and toolbox: it plans before it builds, verifies changes with tests, reviews its own work from a fresh context, remembers what matters, and turns repeated wins into reusable skills

Get the whole plugin