verify

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Verify

验证

Independent validation of
execute
's output. Strict separation of context is the value: a fresh chat reading only the plan and code can spot what an in-context verify would miss.
Compile check (typecheck) has already been run by
/execute
as the safety net there. Verify focuses on test, lint, plan-vs-code judgment, and convention adherence — the work that requires fresh-context judgment.
对
execute
的输出进行独立验证。核心价值在于上下文的严格隔离:仅读取计划和代码的全新会话能够发现上下文内验证会遗漏的问题。
编译检查(typecheck)已由
/execute
作为安全防护步骤执行。Verify 专注于测试、代码检查、计划与代码一致性判断以及规范遵循——这些需要全新上下文判断的工作。

Gate (run first)

前置检查(首先运行)

Required files in
.handoff/
:
config.md
,
plan.md
,
task.md
. If any missing, abort with the matching message:
  • config.md
    missing:
    ❌ No config found. Run
    /setup-handoff
    first.
  • plan.md
    missing:
    ❌ No plan found. Run
    /plan
    first.
  • task.md
    missing:
    ❌ No task found. Run
    /execute
    first.
.handoff/ 目录下需包含以下文件:
config.md
、
plan.md
、
task.md
。若缺少任一文件,将终止执行并返回对应提示信息:
  • 缺少
    config.md
    :
    ❌ 未找到配置文件,请先运行
    /setup-handoff
    。
  • 缺少
    plan.md
    :
    ❌ 未找到计划文件,请先运行
    /plan
    。
  • 缺少
    task.md
    :
    ❌ 未找到任务文件,请先运行
    /execute
    。

Output language

输出语言

All output from this skill — conversational replies to the user, status messages, AND the written
review.md
— uses the language specified by
config.md
's
response_language
. Default if config missing or field absent:
en
. Verification command output (test/typecheck/lint stdout/stderr) is kept verbatim in its original language; your summary of those results uses
response_language
.
本技能的所有输出——包括对用户的对话回复、状态消息以及生成的
review.md
文件——均使用
config.md
中
response_language
指定的语言。若配置文件缺失或该字段未设置,默认使用
en
(英文)。验证命令的输出(测试/类型检查/代码检查的标准输出/错误输出)将保留原始语言的原文;而对这些结果的总结则使用
response_language
指定的语言。

Workflow

工作流程

  1. Read config, plan, task. If plan has
    ## Phases
    , note the active
    [🔄]
    phase — only that phase's change list is in scope for plan-vs-code comparison.
  2. Run verification commands from plan's
    ## Verification plan
    (or fallback to config's test+lint — NOT typecheck). See checks.md for command execution rules.
  3. Compare actual code changes against the active phase's change list — note anything missing or extra. Surface high-risk items first in the report so they can't be glossed over by self-review bias.
  4. Build review.md per review-template.md. Order findings by risk tag (high → medium → low/untagged).
  5. Run cycle close per cycle-close.md: file cleanup + backlog auto-resolve + non-blocking append. For multi-phase plans, this advances phase markers instead of full cleanup unless this is the final phase.
  6. Print summary based on outcome (see cycle-close.md).
  1. 读取配置、计划和任务文件。若计划中包含
    ## Phases
    (阶段)部分,记录带有
    [🔄]
    标记的当前活跃阶段——仅该阶段的变更列表会纳入计划与代码的对比范围。
  2. 执行计划中
    ## Verification plan
    (验证计划)部分指定的验证命令(若未指定,则使用配置文件中的测试+代码检查命令——不包含类型检查)。命令执行规则请参考 checks.md。
  3. 将实际代码变更与当前活跃阶段的变更列表进行对比——记录遗漏或额外的内容。在报告中优先展示高风险项,避免因自我审查偏见而被忽略。
  4. 按照 review-template.md 模板生成 review.md 文件。按风险标签排序展示发现的问题(高→中→低/无标签)。
  5. 按照 cycle-close.md 执行周期收尾操作:文件清理 + 待办项自动解决 + 非阻塞式追加内容。对于多阶段计划,若当前并非最后一个阶段,则仅更新阶段标记而非完全清理。
  6. 根据执行结果打印总结信息(详情请见 cycle-close.md)。

Boundaries

权限边界

  • Allowed: run verification commands, read any file, write
    .handoff/review.md
    , edit
    .handoff/backlog.md
    (resolve 🔄 items, append non-blocking), delete
    .handoff/{plan,task,review}.md
    per cycle-close rules.
  • Forbidden: modify any code, modify
    plan.md
    or
    task.md
    mid-cycle, delete
    .handoff/config.md
    , delete the user's source files.
  • 允许操作: 执行验证命令、读取任意文件、生成
    .handoff/review.md
    、编辑
    .handoff/backlog.md
    (解决带有🔄标记的项、追加非阻塞内容)、按照周期收尾规则删除
    .handoff/{plan,task,review}.md
    。
  • 禁止操作: 修改任何代码、在周期执行过程中修改
    plan.md
    或
    task.md
    、删除
    .handoff/config.md
    、删除用户的源文件。