원클릭으로 Manus에서 모든 스킬 실행

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.

Manus에서 실행

스타212,062

포크32,560

업데이트2026년 6월 7일 08:15

출처

affaan-m

affaan-m/ECC

GitHub 저장소 열기 Creator 저장소 보기

설치 명령

다운로드

Manus에서 실행

SKILL.md

readonly

name	orch-fix-defect
description	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.
origin	ECC

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

이 저장소의 다른 Skills

같은 저장소

continuous-learning-v2

affaan-m/ECC

Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents. v2.1 adds project-scoped instincts to prevent cross-project contamination.

2026-06-10212.1k

orch-add-feature

affaan-m/ECC

Orchestrate building a brand-new feature end to end — research, plan, TDD implementation, review, and gated commit — by delegating each phase to the matching ECC agent. Use when adding a capability that does not exist yet.

2026-06-07212.1k

orch-build-mvp

affaan-m/ECC

Orchestrate bootstrapping a working MVP from a design or spec document — ingest the doc, plan thin vertical slices, scaffold the first end-to-end slice, then TDD-implement, review, and gated commit. Use to turn an SDD/PRD into a running starting point.

2026-06-07212.1k

orch-change-feature

affaan-m/ECC

Orchestrate altering an existing, working feature to new desired behavior — update its tests to the new spec, change the implementation to match, review, and gated commit. Use when behavior is not broken but should be different.

2026-06-07212.1k

orch-pipeline

affaan-m/ECC

Shared orchestration engine for the orch-* skill family. Defines the gated Research-Plan-TDD-Review-Commit pipeline, the size classifier, the agent map, and the two human gates that the orch-* operation skills delegate to. Not usually invoked directly.

2026-06-07212.1k

orch-refine-code

affaan-m/ECC

Orchestrate a behavior-preserving refactor — confirm tests are green, restructure without changing behavior, keep tests green, review, and gated commit. Use when the structure should improve but behavior must not change.

2026-06-07212.1k

name	orch-fix-defect
description	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.
origin	ECC

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