Back to browse

affaan-m/ECC

orch-fix-defect

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. Use when existing behavior is broken or wrong.

80Collecting
See how to use itView GitHub source
npx skills add https://github.com/affaan-m/ECC --skill "skills/orch-fix-defect"
Automated source guideReview and auditStandard source

Source checked Jul 28, 2026·Refresh due Oct 26, 2026

Reorganized from the pinned upstream SKILL.md

Source-grounded review guide: orch-fix-defect

Actor · action · target: orch · fix · defect. Thin wrapper over the shared engine in orch-pipeline.

npx skills add https://github.com/affaan-m/ECC --skill "skills/orch-fix-defect"
Check the pinned source

The pinned source supports a structured brief, but not an expanded tutorial. Only detected inputs, outputs, and sections are shown.

196 source words · 4 usable sections

Best fit

  • 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.

Review workflow

Read orch-fix-defect through these 4 source sections

Sections are extracted automatically from the pinned SKILL.md and link back to the source.

01

When to Use

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

SKILL.md · 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.
02

Operation settings

Default size floor: small (often trivial).

SKILL.md · Operation settings
Default size floor: small (often trivial).Phase mask: 0 → (light 2 only if root cause is non-obvious or standard+) →First move (phase 4): reproduce the bug as a new failing test
03

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…

SKILL.md · 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 redStop at Gate 1 (only if a plan was produced) and Gate 2 (pre-commit).
04

Example

Review the “Example” section in the pinned source before continuing.

SKILL.md · Example
Review and apply the “Example” source section.

Review checklist

Verify each item before delivery

The source section “When to Use” has been checked.

The source section “Operation settings” has been checked.

The source section “How It Works” has been checked.

The source section “Example” has been checked.

Choose a different workflow

When another Skill is the better fit

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.

Open source detail

testing-anti-patterns

Use BEFORE writing/changing tests, adding mocks, or test-only methods on production classes — vs mocking-the-mock, production pollution, partial mocks, and overfit/tautological assertions

A separate implementation from event4u-app/agent-config; compare its source, maintenance signals, and permission requirements.

Open source detail

design-review

Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.

A separate implementation from event4u-app/agent-config; compare its source, maintenance signals, and permission requirements.

Open source detail

FAQ

What does the orch-fix-defect source document cover?

Actor · action · target: orch · fix · defect. Thin wrapper over the shared engine in orch-pipeline.

How do I install orch-fix-defect?

The source record exposes this install command: npx skills add https://github.com/affaan-m/ECC --skill "skills/orch-fix-defect". Inspect the command and pinned source before running it.

Repository stars
234,327
Repository forks
35,711
Quality
80/100
Source repository last pushed

Quality breakdown

Based on traceable docs and repository signals; stars are not treated as quality.

80/100
Documentation19/30
Specificity21/25
Maintenance20/20
Trust signals20/25

Compare before choosing

Related Agent Skills and source variants

These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.

ab-testing by coreyhaines31

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

testing-anti-patterns by event4u-app

Use BEFORE writing/changing tests, adding mocks, or test-only methods on production classes — vs mocking-the-mock, production pollution, partial mocks, and overfit/tautological assertions

design-review by event4u-app

Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.

pest-testing by event4u-app

Use when writing, generating, or improving Pest tests for Laravel — clear intent, good coverage, maintainable structure, and alignment with project testing conventions.

requesting-code-review by event4u-app

Use when asking for a review or creating a PR — self-review first, frame the right context, test plan included — even when the user just says 'open a PR' or 'ready to merge'.

View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 1 min

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:)
Source repo
affaan-m/ECC
Skill path
skills/orch-fix-defect/SKILL.md
Commit SHA
4e973d3eaf92
Repository license
MIT
Data collected