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 match…
它会碰到什么
扫了多少1 个文本文件，2 KB
它会碰到什么不碰外部（只输出文字）
命中总数0 处
命中统计严重 0 · 高 0 · 中 0 · 低 0
这一栏是扫描器报的事实，不是结论。命中多不等于有毒（安全工具、规则库、示例脚本本来就会包含危险写法），命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系，需要你自己看。
技能内容
orch-fix-defect
Actor · action · target: orch · fix · defect. Thin wrapper over the shared
engine in [orch-pipeline](../orch-pipeline/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. - 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-pipelineengine with the settings above. - If the root cause is unclear, scope it with
code-explorerbefore 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-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:)想直接用这个技能？
本站把开放许可（MIT / Apache 等）的技能按仓库打包整理到网盘，点一下转存到你自己的网盘，不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接，不打包。