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>
1.2 KiB
1.2 KiB
description
| description |
|---|
| Orchestrate fixing a bug — reproduce it as a failing regression test, fix to green, review, gated commit. Wrapper for the orch-fix-defect skill. |
/orch-fix-defect
Manually launch the orch-fix-defect orchestrator: prove the bug with a red test, then fix to green.
Usage
/orch-fix-defect <what is broken>
Examples:
/orch-fix-defect poller crashes on empty NWS response
/orch-fix-defect login returns 500 when email has a plus sign
What It Does
Invoke the orch-fix-defect skill with $ARGUMENTS as the request. The skill
(via the shared orch-pipeline engine) will:
- Classify size (default floor: small, often trivial); scope root cause with
code-explorerif unclear. - Write a new failing regression test reproducing the bug, then fix until it goes green. (Proving the bug first is what makes this a fix, not a tweak.)
code-reviewer(+security-reviewerif the defect sits in a sensitive path).- Commit as a conventional
fix:commit. → GATE 2 (confirm before commit).
Use this only when behavior is broken/wrong — not for intentional changes
(/orch-change-feature) or new capability (/orch-add-feature).
If $ARGUMENTS is empty, ask the user to describe the defect.