Orch Fix Defect

When you've got a bug, this orchestrates the full repair cycle: reproduce it as a failing test first, fix it until green, review, then commit. It's the ECC workflow distilled to defect repair specifically, skipping research phase since you already know something's broken. The discipline of red test first is the key move here. It gates at plan review (if generated) and pre-commit, and knows to pull in security review if you're touching sensitive code. If you're changing behavior intentionally rather than fixing what's wrong, you want orch-change-feature instead. Solid structure for turning bug reports into committed fixes without skipping steps.

skills.sh installs: 4.8K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --skill orch-fix-defect --agent claude-code

Installs into .claude/skills of the current project.

Files

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.

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-pipeline engine with the settings above.
If the root cause is unclear, scope it with code-explorer before the red test; escalate build breaks to build-error-resolver / /build-fix.
Stop at Gate 1 (only if a plan was produced) and Gate 2 (pre-commit).
Add security-reviewer if the defect sits in a security-sensitive path.