Orch Fix Defect

Name: Orch Fix Defect
Author: affaan-m

affaan-m/ecc

2 installs
238k repo stars
Updated August 5, 2026
affaan-m/ecc

orch-fix-defect is a Claude Code skill that orchestrates fixing a bug by reproducing it as a failing regression test, fixing to green, reviewing, and committing behind a gate.

About

orch-fix-defect is a Claude Code skill that orchestrates fixing a bug end to end. A developer uses it when existing behavior is broken or wrong, first reproducing the bug as a new failing regression test, then fixing to green, reviewing, and committing behind a gate. It is a thin wrapper over the shared orch-pipeline engine and can scope unclear root causes with code-explorer.

Orchestrates fixing a bug by reproducing it as a failing regression test, then fixing to green
Delegates each phase to the matching ECC agent through the shared orch-pipeline engine
Escalates unclear root causes to code-explorer and build breaks to build-error-resolver

Orch Fix Defect by the numbers

2 all-time installs (skills.sh)
Ranked #13,958 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
Data as of Aug 5, 2026 (Skillselion catalog sync)

At a glance

orch-fix-defect capabilities & compatibility

Capabilities: agent orchestration · bug fixing · regression testing · code review
Works with: github
Use cases: orchestration · debugging · testing

From the docs

What orch-fix-defect says it does

Orchestrate fixing a bug — reproduce it as a failing regression test, fix to green, review, and gated commit

SKILL.md

Something is **broken**: wrong output, an error, a crash, a regression.

SKILL.md

npx skills add https://github.com/affaan-m/ecc --skill orch-fix-defect

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

[![Listed on Skillselion](https://skillselion.com/badge/skills/affaan-m/ecc/orch-fix-defect.svg)](https://skillselion.com/skills/affaan-m/ecc/orch-fix-defect)

Installs	2
repo stars	★ 238k
Last updated	August 5, 2026
Repository	affaan-m/ecc ↗

What it does

Orchestrate a bug fix by reproducing the defect as a failing regression test, fixing to green, reviewing, and gated commit.

Who is it for?

Fixing broken or wrong behavior with a regression test written first.

Skip if: Changing correct-but-undesired behavior (orch-change-feature) or adding a new capability (orch-add-feature).

When should I use this skill?

Something is broken: wrong output, an error, a crash, or a regression.

What you get

A failing regression test that reproduces the bug, a fix that turns it green, reviewed and committed as a fix: commit.

Failing regression test reproducing the bug
Fix that turns tests green
Reviewed fix: commit

By the numbers

Phase mask 0-(2)-4-5-6
2 human gates

Files

SKILL.mdMarkdownGitHub ↗

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

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:)