orch-fix-defect

Name: orch-fix-defect
Author: affaan-m

Orchestrate bug fixing from repro to gated commit with delegated agents.

Stars

★ 229,796

Source

GitHub

Updated

2026-07-15

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 229.8k

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "orch-fix-defect" skill from askskill:
1. Download https://raw.githubusercontent.com/affaan-m/ECC/main/skills/orch-fix-defect/SKILL.md
2. Save it as ~/.claude/skills/orch-fix-defect/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Fix a production regression

Prompt

Orchestrate a bug-fix workflow: first reproduce the issue and write a failing regression test, then implement the fix until tests pass, then perform code review, and finally commit only after all gates pass. Issue: users cannot log in after resetting their password, and the API returns 500.

Expected

A staged bug-fix result including failing tests, the code fix, review feedback, and a gated commit outcome.

Add regression coverage and fix a historical bug

Prompt

Please orchestrate a full bug-fix flow for this historical defect: find minimal reproduction steps, generate a failing regression test, fix the code and verify related tests pass, then provide a review summary and complete a gated commit. Defect: usernames containing Chinese characters become garbled when exporting CSV.

Expected

A complete fix package with minimal reproduction, regression tests, code changes, verification results, and a pre-commit review summary.

Fix incorrect API behavior

Prompt

Help orchestrate fixing this API defect: first turn the incorrect behavior into a reproducible failing test, then implement the fix and pass related tests, then run code review, and commit only after gates are satisfied. Problem: when inventory is 0, the order API still returns success.

Expected

Outputs a phase-by-phase fix result showing failure-to-green testing, review conclusions, and final commit status.

// docs

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.

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