Comet Verify
Use when Comet change 已完成 build 阶段,需要验证实现、处理验证失败决策或完成分支收尾。
Install
npx skills add rpamis/comet --skill comet-verifygit clone --depth 1 https://github.com/rpamis/comet.git /tmp/comet
mkdir -p ~/.claude/skills
cp -r /tmp/comet/eval/local/skills/benchmarks/040-beta/comet-verify ~/.claude/skills/comet-verifyPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Comet 阶段 4:验证与收尾(Verify) ## 前置条件 - 代码已提交(阶段 3 完成) - tasks.md 全部任务已完成 ## 步骤 ### 0a. 输出语言约束 验证报告和分支处理说明必须使用触发本次工作流的用户请求语言。 ### 0b. 入口状态验证(Entry Check) 按 `comet/reference/scripts.md` 定位脚本(定位 `comet-env.mjs`),然后执行入口验证;从任意入口恢复时先按 `comet/reference/context-recovery.md` 运行恢复检查: ```bash node "$COMET_STATE" check <change-name> verify ``` 验证通过后继续 Step 1。验证失败时脚本会输出具体失败原因。 **幂等性**:verify 阶段所有检查可安全重复执行。如 `verify_result` 已为 `pass` 且 `branch_status` 已为 `handled`,说明验证已完成,直接执行 guard 流转。如 `verify_result` 为 `pending`,从头开始验证。 ### 1. 改动规模评估 执行规模评估: ```bash node "$COMET_STATE" scale <change-name> ``` 脚本自动统计任务数、增量规格数、变更文件数,判断使用 light 或 full 验证模式,并设置 verify_mode 字段。判定规则(满足任一即 full):任务数 > 3、delta spec 能力数 > 1、变更文件数 > 8。 验证开始前,按 `comet/reference/dirty-worktree.md` 协议检查并处理未提交改动。verify 阶段的特殊处理: 1. 若 dirty diff 属于当前 change 且涉及实现、测试、tasks、delta spec 或 design doc 变更,不在 verify 阶段直接修复或提交;报告失败项并进入 Step 1b 的验证失败决策阻塞点 2. 若 dirty diff 只是 verify 本阶段产物(例如验证报告草稿、分支处理记录),可继续在 verify 阶段完成并记录状态 3. 若 dirty diff 已实现但 tasks.md 未勾选,视为 build 状态滞后;报告失败项并进入 Step 1b,由用户决定回退修复或接受偏差 用户选择修复后,才允许回退到 build 阶段: ```bash # 仅在用户确认修复后执行 node "$COMET_STATE" transition <change-name> verify-fail ``` 注意:verify-fail 回退到 build 时 `branch_status` 不会被重置。如果首次 verify 已完成分支处理,修复后再次进入 verify 时跳过已完成的分支处理步骤,直接使用 `node "$COMET_STATE" set <change-name> branch_status handled` 保留原有分支处理结果。 注意:如果 build 阶段每个任务都已提交,脚本基于工作区 diff 的文件数可能低估改动规模。此时必须读取 plan 文件头的 `base-ref` 并用提交区间复核:
Details
- Skill name
comet-verify- Repository
- rpamis/comet
- Path
eval/local/skills/benchmarks/040-beta/comet-verify/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
FAQ
What does the Comet Verify skill do?
Use when Comet change 已完成 build 阶段,需要验证实现、处理验证失败决策或完成分支收尾。
How do I install the Comet Verify skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add rpamis/comet --skill comet-verify. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Comet Verify popular?
It lives in rpamis/comet, which has 3,306 GitHub stars and 317 forks.
Related skills
Brainstorming
3.3krpamis/comet
Transforms rough ideas into fully-formed designs. Structure your brainstorming sessions and develop ideas systematically.
Dispatching Parallel Agents
3.3krpamis/comet
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Finishing a Development Branch
3.3krpamis/comet
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Openspec Bulk Archive Change
3.3krpamis/comet
Archive multiple completed changes at once. Use when archiving several parallel changes.
Comet Verify
3.3krpamis/comet
Verify a Classic change and record the results. Use when the user invokes /comet-verify or Classic Runtime enters Verify.
Openspec Ff Change
3.3krpamis/comet
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.