Agent Skills
› NeverSight/learn-skills.dev
› orch-fix-defect
orch-fix-defect
GitHub用于修复现有代码缺陷。通过委派给ECC代理，依次完成复现（编写失败回归测试）、修复、审查及门禁提交。适用于输出错误、崩溃或回归等场景，强调先证明Bug存在再修复。
Trigger Scenarios
代码行为异常或输出错误
程序发生崩溃或报错
发现已存在的功能回归
Install
npx skills add NeverSight/learn-skills.dev --skill orch-fix-defect -g -y
SKILL.md
Frontmatter
{
"name": "orch-fix-defect",
"origin": "ECC",
"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."
}
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.
- behavior is correct but you want it different →
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-pipelineengine with the settings above. - If the root cause is unclear, scope it with
code-explorerbefore the red test; escalate build breaks tobuild-error-resolver//build-fix. - Stop at Gate 1 (only if a plan was produced) and Gate 2 (pre-commit).
- Add
security-reviewerif 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:)
Version History
- e0220ca Current 2026-07-05 23:59
