orch-fix-defect

SkillAI & models

orch-fix-defect is a skill for AI agents that orchestrates fixing a bug. It runs a pipeline where the agent first reproduces the defect as a failing regression test, then fixes the code until that test passes. Each phase is delegated to the matching ECC agent, and the skill pauses for human confirmation at review and pre-commit gates before committing.

Use orch-fix-defect in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add orch-fix-defect and connect your AI. About a minute.

Also: Claude Code · Cursor · Codex

Then ask your AI: use the orch-fix-defect skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Have an AI agent that can load and run skills.

orch-fix-defectStart free

What your AI can do with it

  • Reproduce a defect as a new failing regression test
  • Fix code until the regression test passes
  • Delegate unclear root causes to a code-exploring agent
  • Pause for human confirmation at review and pre-commit gates
  • Commit the fix only after the gates are confirmed

Getting started

  1. Have an AI agent that can load and run skills.
  2. Add the orch-fix-defect skill to that agent.
  3. Make sure the matching ECC agents are available for delegation.
  4. Point the agent at the broken behavior and start the skill.

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.

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

  1. Run the orch-pipeline engine with the settings above.
  2. If the root cause is unclear, scope it with code-explorer before the red test; escalate build breaks to build-error-resolver / /build-fix.
  3. Stop at Gate 1 (only if a plan was produced) and Gate 2 (pre-commit).
  4. Add security-reviewer if 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
270k
Forks
40k
Last commit
Sep 2026

Questions

When should I use this skill?
Use it when existing behavior is broken or wrong and you want the agent to fix the bug through a test-first pipeline.
Does it commit the fix automatically?
No. It pauses for human confirmation at review and pre-commit gates before committing.
What happens if the root cause is unclear?
The skill can delegate the unclear root cause to a code-exploring agent.
What does the agent do first?
It reproduces the defect as a new failing regression test before changing any code.
How does it know the fix is done?
The fix is done when the new regression test passes.
Advanced
Item type
skill
Key
orch-fix-defect
Source
github.com/affaan-m/ecc