affaan-m/ECC

orch-refine-code

Orchestrate a behavior-preserving refactor — confirm tests are green, restructure without changing behavior, keep tests green, review, and gated commit. Use when the structure should improve but behavior must not change.

80Collecting
See how to use itView GitHub source
npx skills add https://github.com/affaan-m/ECC --skill "skills/orch-refine-code"
Automated source guideReview and auditStandard source

Source checked Jul 28, 2026·Refresh due Oct 26, 2026

Reorganized from the pinned upstream SKILL.md

Source-grounded review guide: orch-refine-code

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

npx skills add https://github.com/affaan-m/ECC --skill "skills/orch-refine-code"
Check the pinned source

The pinned source supports a structured brief, but not an expanded tutorial. Only detected inputs, outputs, and sections are shown.

204 source words · 4 usable sections

Best fit

  • Same behavior, better structure: extract modules, remove duplication, kill
  • Distinguish from siblings: if behavior is meant to change at all, this is the

Review workflow

Read orch-refine-code through these 4 source sections

Sections are extracted automatically from the pinned SKILL.md and link back to the source.

01

When to Use

Same behavior, better structure: extract modules, remove duplication, kill

SKILL.md · When to Use
Same behavior, better structure: extract modules, remove duplication, killDistinguish from siblings: if behavior is meant to change at all, this is the- 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 (or…
02

Operation settings

Default size floor: standard — restructures touch multiple files.

SKILL.md · Operation settings
Default size floor: standard — restructures touch multiple files.Phase mask: 0 → 2 (plan the restructure) → 4 (keep green) → 5 → 6. No newFirst move (phase 4): confirm the relevant tests exist and are green
03

How It Works

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

SKILL.md · How It Works
Run the orch-pipeline engine with the settings above.For dead-code / duplication sweeps, delegate to the refactor-cleaner agentStop at Gate 1 (restructure plan) and Gate 2 (pre-commit).
04

Example

Review the “Example” section in the pinned source before continuing.

SKILL.md · Example
Review and apply the “Example” source section.

Review checklist

Verify each item before delivery

The source section “When to Use” has been checked.

The source section “Operation settings” has been checked.

The source section “How It Works” has been checked.

The source section “Example” has been checked.

Choose a different workflow

When another Skill is the better fit

FAQ

What does the orch-refine-code source document cover?

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

How do I install orch-refine-code?

The source record exposes this install command: npx skills add https://github.com/affaan-m/ECC --skill "skills/orch-refine-code". Inspect the command and pinned source before running it.

Repository stars
234,327
Repository forks
35,711
Quality
80/100
Source repository last pushed

Quality breakdown

Based on traceable docs and repository signals; stars are not treated as quality.

80/100
Documentation19/30
Specificity21/25
Maintenance20/20
Trust signals20/25

Compare before choosing

Related Agent Skills and source variants

These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.

View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 1 min

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

  1. Run the orch-pipeline engine with the settings above.
  2. For dead-code / duplication sweeps, delegate to the refactor-cleaner agent (it runs knip / depcheck / ts-prune and removes safely).
  3. Stop at Gate 1 (restructure plan) and Gate 2 (pre-commit).
  4. 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]
Source repo
affaan-m/ECC
Skill path
skills/orch-refine-code/SKILL.md
Commit SHA
4e973d3eaf92
Repository license
MIT
Data collected