Skill

orch-refine-code

From ecc

Orchestrates behavior-preserving refactors: confirm tests green, restructure in small steps, keep tests green, review, and gated commit. Use when structure should improve but behavior must not change.

developer-tools

npx claudepluginhub affaan-m/ecc --plugin ecc

Popularity

Stars

213,662

Forks

32,845

Shared by

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/ecc:orch-refine-code

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Actor · action · target: **orch · refine · code**. Thin wrapper over the shared

SKILL.md

44 lines · ~445 tokens

Similar Skills

refactoring

Guides safe code refactoring with test-first steps, common refactor patterns, and anti-patterns to avoid.

SCALE Engine

refactor

Orchestrates a multi-step refactoring pipeline: analyzes code quality, plans improvements, optionally writes tests, implements changes, and reviews results. Routes simple refactors to a lighter workflow.

Claude Setup

acp-refactor

Refactors code while preserving behavior: cleanup, modularize, deduplicate, rename, simplify structure in small reversible steps. Not for behavioral changes.

agent-coding-playbook

Stats

LanguageJavaScript

Stars213,662

Forks32,845

MaintenanceExcellent

Last CommitJun 11, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

orch-refine-code

Actor · action · target: orch · refine · code. Thin wrapper over the shared engine in orch-pipeline.

When to Use

Same behavior, better structure: extract modules, remove duplication, kill dead code, reduce nesting, rename for clarity.

Distinguish from siblings: if behavior is meant to change at all, this is the wrong skill (orch-change-feature / orch-fix-defect).

Operation settings

Default size floor: standard — restructures touch multiple files.

Phase mask: 0 → 2 (plan the restructure) → 4 (keep green) → 5 → 6. No new behavior tests are written — the existing suite is the safety net.

First move (phase 4): confirm the relevant tests exist and are green before touching code; if coverage is thin, add characterization tests first. Then restructure in small steps, re-running tests after each.

How It Works

Run the orch-pipeline engine with the settings above.

For dead-code / duplication sweeps, delegate to the refactor-cleaner agent (it runs knip / depcheck / ts-prune and removes safely).

Stop at Gate 1 (restructure plan) and Gate 2 (pre-commit).

Commit as refactor: — the diff must be behavior-neutral.

Example

orch-refine-code: extract the NWS HTTP client out of poller.py → confirm tests green → plan extraction [GATE 1: approve] → move in small steps, tests green throughout → code-review → commit refactor: [GATE 2: confirm]

orch-refine-code

Actor · action · target: orch · refine · code. Thin wrapper over the shared engine in orch-pipeline.

When to Use

Same behavior, better structure: extract modules, remove duplication, kill dead code, reduce nesting, rename for clarity.
Distinguish from siblings: if behavior is meant to change at all, this is the wrong skill (orch-change-feature / orch-fix-defect).

Operation settings

Default size floor: standard — restructures touch multiple files.
Phase mask: 0 → 2 (plan the restructure) → 4 (keep green) → 5 → 6. No new behavior tests are written — the existing suite is the safety net.
First move (phase 4): confirm the relevant tests exist and are green before touching code; if coverage is thin, add characterization tests first. Then restructure in small steps, re-running tests after each.

How It Works

Run the orch-pipeline engine with the settings above.
For dead-code / duplication sweeps, delegate to the refactor-cleaner agent (it runs knip / depcheck / ts-prune and removes safely).
Stop at Gate 1 (restructure plan) and Gate 2 (pre-commit).
Commit as refactor: — the diff must be behavior-neutral.

Example

orch-refine-code: extract the NWS HTTP client out of poller.py
→ confirm tests green → plan extraction  [GATE 1: approve]
→ move in small steps, tests green throughout → code-review
→ commit refactor:  [GATE 2: confirm]

orch-refine-code

Popularity

Invocation

Context Preview

SKILL.md

Similar Skills

Help us improve

Help us improve

Find plugins for your project

orch-refine-code

Popularity

Invocation

Context Preview

SKILL.md

orch-refine-code

When to Use

Operation settings

How It Works

Example

Similar Skills

Help us improve

orch-refine-code

When to Use

Operation settings

How It Works

Example