repair

name: Repair description: | 云效缺陷单修复流程 skill。用于处理已经由共享 Phase 0 拉取到 /media/yhr/2T/yunxiao/bugs/<bug-id>/ 的缺陷单，四阶段：Intake 读取缺陷单、切输入分支、结合代码分析、生成 root-cause.md、fix_plan.json 和 Breach 对齐页、将状态改为 修复中；Fix 按修复方案和 Neutralize 工作流修复，按条件 触发 Codify 和 AfterAction；Closeout 改为 集成测试中；Clear 合入主分支打包关闭。

Make sure to use this skill when the user says 处理缺陷、修复缺陷单、 bug 单、云效缺陷、进入修复中、提交回归验证、缺陷误报、缺陷转需求， or invokes /Repair Intake, /Repair Fix, /Repair Closeout, /Repair Clear.

Do NOT use for general code debugging without a Yunxiao bug id; use Neutralize for ordinary bugfix/debug requests. Repair never changes bug assignee/owner.

Repair — 云效缺陷修复流程

一个 skill，四个 mode。缺陷单原始上下文由共享 Phase 0 生成，Repair 只负责接单分析、修复和收尾。

路由

参数不匹配任何 mode 时，列出上表用法。匹配后立即读取对应 mode 文件执行完整流程。

全局约定

• 缺陷目录: /media/yhr/2T/yunxiao/bugs/<bug-id>/ — Phase 0 原始材料和 state.json 的存放位置，Repair 只读
• 产物目录: .proposal/repair/<bug-id>/ — 所有 Intake 生成的产物（root-cause.md、fix_plan.json、Breach HTML）写入当前 repo 的此路径
• Phase 0: 与需求开发共用同一个 yunxiao 定时任务；只抓取、下载、创建本地文件、发通知，不改云效状态
• 输入状态: Phase 0 当前样本已生成 state.json、detail.md，图片/日志附件可平铺在缺陷目录
• 状态集合: 待处理、重新打开、修复中、开发挂起、集成测试中、回归验证、转需求、关闭
• 负责人规则: 全流程不修改负责人；只读负责人字段，只修改评论区和缺陷状态
• 分支规则: --base <branch> 从 base 创建 bugfix/<bug-id>；dirty worktree 停止，不自动 stash
• Breach 页面: 每次 Intake 必生成 .proposal/repair/<bug-id>/index.html
• 缺字段策略: 先用现有 state.json；Intake 能从云效实时补查就写回，补不到关键字段再问用户

Workflow Gate Contract

Repair modes must satisfy the shared workflow output contract:

/home/yhr/.agents/repos/agent-skills/references/skill-output-contract.md

Each mode must leave a resumable handoff: state.json, Canon task page, update card, and mode-specific artifacts (root-cause.md + fix_plan.json, Breach page, fix_gate.json, Sentinel state, commit/MR, or Closeout comment).

Resources

• intake.md — Intake phase execution instructions
• fix.md — Fix phase execution instructions
• closeout.md — Closeout phase execution instructions
• clear.md — Clear phase execution instructions
• references/fix_plan_schema.md — fix_plan.json schema + gate behavior
• references/fix_result_schema.md — fix_result.json schema + gate behavior
• scripts/intake_gate.py — Intake gate checker
• scripts/fix_gate.py — Fix gate checker
• scripts/closeout_gate.py — Closeout gate checker
• Runtime artifacts: fix_gate.json, closeout_gate.json (each phase's entry defense)

Gotchas

• Yunxiao status updates require status IDs from get_work_item_workflow; do not pass Chinese display names such as 修复中 or 回归验证 to update APIs.
• Repair never changes the defect assignee/owner. Only comments and defect status are mutable unless the user explicitly changes this rule.
• Fix may run Sentinel builds/tests; Closeout must not start a new build. Closeout consumes self_check_summary, deliverable links, and Review Gate evidence from Fix.
• Every outcome needs a Yunxiao comment. Fixed, false positive, transferred-to-demand, and closed all need explicit evidence or clarification text.
• Do not enter Closeout until Review Gate blockers are fixed or explicitly waived.
• Clear is the only phase that merges to the base branch and starts a new package build. It must only run after the tester confirms regression verification.

Canon 输出边界

读取共享契约：/home/yhr/.agents/repos/agent-skills/references/canon-output-contract.md。

• <bug_root>/state.json 是 Phase 0/Repair 阶段门控文件，<repo_root>/.proposal/repair/<bug-id>/ 是修复方案 artifact 目录。
• 缺陷长期状态写入 Canon task page：/media/yhr/2T/Canon/tasks/<bug-id>.md，记录根因、修复分支、验证证据、交付物、云效状态和下一步。
• root-cause.md、Breach HTML、Sentinel task、commit/MR、镜像 HTTP 链接、AfterAction/Codify 产物都作为 Canon artifact refs。
• 每个 mode 完成后创建或更新 /media/yhr/2T/Canon/raw/update-cards/<date>-repair-<bug-id>-<mode>.md。
• Repair 全流程不修改负责人；Canon 也只记录 owner/validator 信息，不把它当作状态修改动作。

State 更新边界

不要覆盖自己负责范围外的字段。