Back to Details

orch-fix-defect

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

orch-fix-defect

orch-fix-defect

Actor · action · target: orch · fix · defect. Thin wrapper over the shared engine in 
orch-pipeline
.
角色·操作·目标：orch · fix · defect。是对
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
      .
  • 当功能出现故障时：输出错误、报错、崩溃、回归问题。
  • 与同类技能区分：
    • 行为正确但需要调整 → 使用
      orch-change-feature
      。
    • 功能尚未存在 → 使用
      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.
  • 默认规模下限：小型（通常简单）。
  • 阶段掩码：0 →（仅当根本原因不明确或属于标准以上级别时才启用阶段2）→4→5→6。研究阶段（1）通常会跳过。
  • 第一步（阶段4）：将缺陷重现为新的失败测试（回归测试），然后修复至测试通过。先证明缺陷存在是区分“修复”和“微调”的关键。

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.
  1. 使用上述设置运行
    orch-pipeline
    引擎。
  2. 如果根本原因不明确，在编写失败测试前使用
    code-explorer
    确定范围；将构建失败问题升级至
    build-error-resolver
    / 
    /build-fix
    处理。
  3. 在Gate 1（仅当生成了修复计划时）和Gate 2（提交前）处暂停。
  4. 如果缺陷位于安全敏感路径中，添加
    security-reviewer
    参与处理。

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