mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-06-11 02:33:10 +08:00
90dfd9505d
* feat: add orch-* orchestrator skill family Lightweight wrappers that orchestrate existing ECC agents through a gated Research -> Plan -> TDD -> Review -> Commit pipeline, right-sized per task. - orch-pipeline: shared engine (phases, size classifier, two gates, agent map) - orch-add-feature/change-feature/fix-defect/refine-code/build-mvp: thin wrappers delegating to the engine * chore: register orch-* family in catalog, command registry, and agent.yaml (post-rebase onto green main) --------- Co-authored-by: ECC Test <ecc@example.test>
40 lines
1.4 KiB
Markdown
40 lines
1.4 KiB
Markdown
---
|
|
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.
|