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

Files1

1 files · 1.0 KB

Select a file to preview

Overall Score

78/100

Grade

B

Good

Safety

85

Quality

76

Clarity

82

Completeness

68

Summary

An orchestration skill that coordinates bug-fixing workflows by delegating to specialized ECC agents. It wraps the shared `orch-pipeline` engine with defect-specific settings: a phase mask to focus on test-driven diagnosis and fixes, and gated commit reviews to ensure quality.

Detected Capabilities

orchestration of sub-agentsdelegation to specialized skills (orch-pipeline, code-explorer, build-error-resolver, security-reviewer)test-driven bug reproductiongated workflow checkpointsphase masking to control workflow scope

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

fix regression testreproduce bugdebug crashrepair broken featuretest-driven debugging

Use Cases

Reproduce a reported bug as a failing regression test to verify the defect exists, then iterate toward a fix
Diagnose and repair non-obvious root causes by invoking code exploration before writing the test
Manage security-sensitive bug fixes by invoking a security reviewer as part of the workflow
Escalate build failures or complex breakages to specialized error-resolution agents
Gate fixes at two checkpoints — after diagnosis/planning (Gate 1) and before commit (Gate 2) — to ensure quality and prevent regressions

Quality Notes

Well-scoped and tightly focused: clearly distinguishes defect-fixing from feature requests (change/add)
Example is concrete and shows end-to-end workflow with a realistic scenario
Clear phase mask guidance (0 → 2 → 4 → 5 → 6, skipping 1) helps control complexity
Gating strategy (Gate 1 & 2) is well-documented and prevents premature commits
Leverages shared engine (`orch-pipeline`) avoiding duplication and maintaining consistency
References dependencies (code-explorer, build-error-resolver, security-reviewer) but does not document their behavior — assumes reader familiarity with ECC ecosystem
Operation settings section is concise but could benefit from slightly more detail on what 'small (often trivial)' size floor means in practice
Does not document failure modes or error handling — e.g., what if Gate 1 rejects the plan?

Model: claude-haiku-4-5-20251001Analyzed: Jun 7, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

orch-fix-defect

orch-fix-defect

When to Use

Operation settings

How It Works

Example

Summary

Detected Capabilities

Trigger Keywords

Use Cases

Quality Notes

Reviews

Command Palette