Orch Fix Defect Skill
- 1.1k installs
- 239k repo stars
- Updated August 11, 2026
- affaan-m/everything-claude-code
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 gated-committing via the shared orch-pipeline.
About
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 gated-committing. It is a thin wrapper over the shared orch-pipeline engine that delegates each phase to the matching ECC agent, scoping unclear root causes with code-explorer and escalating build breaks to build-error-resolver. A developer uses it when existing behavior is broken (wrong output, an error, a crash, or a regression), distinct from changing or adding a feature.
- 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 cause to code-explorer and build breaks to build-error-resolver; commits with a fix: prefix
Orch Fix Defect by the numbers
- 1,105 all-time installs (skills.sh)
- +104 installs in the week ending Aug 10, 2026 (Skillselion tracking)
- Ranked #49 of 611 Debugging skills by installs in the Skillselion catalog
- Data as of Aug 11, 2026 (Skillselion catalog sync)
orch-fix-defect capabilities & compatibility
- Capabilities
- debugging · regression testing · orchestration · code review
- Use cases
- debugging · testing · code review
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 — by delegating each phase to the matching ECC agent.
Something is **broken**: wrong output, an error, a crash, a regression.
npx skills add https://github.com/affaan-m/everything-claude-code --skill orch-fix-defectAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.1k |
|---|---|
| repo stars | ★ 239k |
| Last updated | August 11, 2026 |
| Repository | affaan-m/everything-claude-code ↗ |
What it does
Orchestrate fixing a bug by writing a failing regression test, fixing to green, reviewing, and committing.
Who is it for?
Fixing broken behavior - wrong output, an error, a crash, or a regression - with a reproducing regression test.
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 reproducing regression test that fails then passes after the fix, reviewed and committed with a fix: prefix.
- Failing regression test
- fix to green
- code review and gated commit with fix: prefix
By the numbers
- Phase mask 0-(light 2)-4-5-6
- default size floor small
- commits with a fix: prefix
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
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:)Related skills
Azure DiagnosticsSystematically diagnose and resolve production issues on Microsoft Azure using official Microsoft guidance.508k1.4kAzure MessagingQuickly diagnose and fix connection, authentication, and message-processing failures when using Azure Event Hubs or Service Bus SDKs.496k1.4k
Diagnosing BugsGet a systematic, step-by-step process that surfaces the real root cause instead of guessing at bugs.336k210k
Use My BrowserWhen their agent task requires access to the live browser session, rendered DOM state, authenticated dashboards, localhost apps, or DevTools-selected elements instea269k71
Systematic DebuggingFollow a repeatable four-phase process that forces root-cause discovery before any code changes.216k269k
Safe DebugGet conservative, non-destructive diagnosis of deep learning and agent errors before any code changes are made.199k511FAQ
What is its first move?
Reproduce the bug as a new failing regression test, then fix until it goes green.
What if the root cause is unclear?
It scopes the root cause with code-explorer before the red test and escalates build breaks to build-error-resolver or /build-fix.