Orch fix defect
Orchestrate fixing a bug — reproduce it as a failing regression test, fix to green, review, and gated commit — by delegating each phase to the matching ECC agent. Use when existing behavior is broken or wrong.From its SKILL.md
npx -y skills add Adaptive-Liquidity/aeon-lab --skill orch-fix-defectAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.6 KB, as published. Nobody here has run it
orch-fix-defect
Actor · action · target: orch · fix · defect. Thin wrapper over the shared
engine in orch-pipeline.
When to Use
- Something is broken: wrong output, an error, a crash, a regression.
- Distinguish from siblings:
- behavior is correct but you want it different →
orch-change-feature. - the capability does not exist yet →
orch-add-feature.
- behavior is correct but you want it different →
Operation settings
- Default size floor: small (often trivial).
- Phase mask: 0 → (light 2 only if root cause is non-obvious or standard+) → 4 → 5 → 6. Research (1) is usually skipped.
- First move (phase 4): reproduce the bug as a new failing test (regression test), then fix until it goes green. Proving the bug exists first is what separates a fix from a tweak.
How It Works
- Run the
orch-pipelineengine with the settings above. - If the root cause is unclear, scope it with
code-explorerbefore the red test; escalate build breaks tobuild-error-resolver//build-fix. - Stop at Gate 1 (only if a plan was produced) and Gate 2 (pre-commit).
- Add
security-reviewerif the defect sits in a security-sensitive path.
Example
orch-fix-defect: poller crashes on empty NWS response
→ write failing test reproducing the crash → fix to green
→ code-review → commit [GATE 2: confirm] (commit: fix:)