orch-fix-defect
SkillAI & modelsorch-fix-defect is a skill that orchestrates fixing a bug through a structured pipeline: reproduce the defect as a failing regression test, apply fixes until tests go green, run a code review, and commit behind a confirmation gate. It delegates each phase to the matching ECC agent, so the person using an AI agent gets a repeatable bug-fix workflow instead of ad-hoc patching.
Available today. Use it from your connected AI after setup.
No other account needed.
Have the ECC agents available that the skill delegates to, including the shared orch-pipeline engine.
Then ask your AI: use the orch-fix-defect skill
What your AI can do with it
- Reproduce a bug as a new failing regression test before fixing it
- Apply fixes until the test suite goes green
- Scope unclear root causes beforehand using code-explorer
- Escalate build breaks to build-error-resolver / /build-fix
- Run a code review phase, adding security-reviewer for security-sensitive paths
- Gate commits behind explicit pre-commit confirmation
Getting started
- Have the ECC agents available that the skill delegates to, including the shared orch-pipeline engine.
- Add the orch-fix-defect skill to your agent's skill set.
- Invoke it when existing behavior is broken or wrong, describing the defect (for example, a crash or wrong output).
- If the root cause is unclear, let the skill scope it with code-explorer before writing the failing test.
- Confirm the commit at the pre-commit gate after review passes.
What this skill tells your AI
The instructions your AI receives, as published by affaan-m/ecc in skills/orch-fix-defect/SKILL.md and read by ahel’s review.
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:)
Signals
- GitHub stars
- 268k
- Forks
- 40k
- Last commit
- Sep 2026
Questions
- When should I use this instead of a sibling skill?
- Use orch-fix-defect when something is broken: wrong output, an error, a crash, or a regression. If behavior is correct but you want it different, use orch-change-feature; if the capability does not exist yet, use orch-add-feature.
- Why write a failing test first?
- Proving the bug exists first is what separates a fix from a tweak. The skill reproduces the defect as a new failing regression test, then fixes until it goes green.
Advanced
- Item type
- skill
- Key
orch-fix-defect- Source
- github.com/affaan-m/ecc