[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72W1PH2TASZ2QDCC9HHGGK8":3,"skill-same:01M72W1PH2TASZ2QDCC9HHGGK8":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M72W1PH2TASZ2QDCC9HHGGK8","comet-archive",null,"Use when Comet change 验证已通过，需要用户确认归档、合并 delta spec，或恢复 archive 阶段。","rpamis\u002Fcomet","rpamis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F153429891?v=4","01M72VXBR7EQYMM7KN8C19244V","01M72VXBRYC06QG0ZH0JBGV09V",3298,"MIT","https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Feval\u002Flocal\u002Fskills\u002Fbenchmarks\u002F040-beta\u002Fcomet-archive\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: comet-archive\ndescription: \"Use when Comet change 验证已通过，需要用户确认归档、合并 delta spec，或恢复 archive 阶段。\"\n---\n\n# Comet 阶段 5：归档（Archive）\n\n## 前置条件\n\n- 验证已通过（阶段 4 完成）\n- 分支已处理\n- `openspec\u002Fchanges\u002F\u003Cname>\u002F.comet.yaml` 中 `verify_result: pass`\n\n## 步骤\n\n### 0. 输出语言约束\n\n归档摘要和生命周期闭环说明必须使用触发本次工作流的用户请求语言。\n\n### 0b. 入口状态验证（Entry Check）\n\n按 `comet\u002Freference\u002Fscripts.md` 定位脚本（定位 `comet-env.mjs`），然后执行入口验证；从任意入口恢复时先按 `comet\u002Freference\u002Fcontext-recovery.md` 运行恢复检查：\n\n```bash\nnode \"$COMET_STATE\" check \u003Cname> archive\n```\n\n验证通过后继续 Step 1。验证失败时脚本会输出具体失败原因。\n\n### 1. 归档前最终确认（阻塞点）\n\n入口验证通过后，**必须按 `comet\u002Freference\u002Fdecision-point.md` 的协议暂停并等待用户确认是否立即归档**。不得在用户确认前运行 `node \"$COMET_ARCHIVE\" \"\u003Cchange-name>\"`。\n\n确认前必须向用户展示简短摘要：\n- change 名称\n- 验证报告路径和结论\n- 分支处理状态\n- 本次归档将执行的不可逆动作：按 OpenSpec delta 语义合并主 spec、标注 design doc \u002F plan、移动 change 到 archive 目录\n\n用户确认问题必须以单选题形式呈现，包含以下选项：\n- 「确认归档」— 立即执行归档脚本，完成 spec 合并和 change 移动\n- 「需要调整或重新验证」— 不执行归档；运行 `node \"$COMET_STATE\" transition \u003Cchange-name> archive-reopen` 回到 `phase: verify`，再调用 `\u002Fcomet-verify`。若验证阶段确认需要修复，再按 `\u002Fcomet-verify` 的验证失败决策回到 `\u002Fcomet-build`\n- 「暂不归档」— 不执行归档，保留当前 `phase: archive` 状态，等待用户稍后再次调用 `\u002Fcomet-archive`\n\n只有用户选择「确认归档」后，才允许继续 Step 2。用户选择「需要调整或重新验证」后，必须先执行 `archive-reopen` 状态回退，不得手动编辑 `.comet.yaml`。\n\n### 2. 执行归档\n\n运行归档脚本，自动完成以下全部步骤：\n\n```bash\nnode \"$COMET_ARCHIVE\" \"\u003Cchange-name>\"\n```\n\n脚本自动执行：\n1. 入口状态验证（phase=archive, verify_result=pass, archived=false）\n2. Design doc 前置元数据标注（archived-with, status）\n3. Plan 前置元数据标注（archived-with）\n4. 调用 OpenSpec archive 按 delta 语义合并主 spec 并移动 change 到归档目录\n5. 校验主 spec 未残留 delta-only section 标题\n6. 在 OpenSpec 实际归档目录中更新 archived 状态，并协调 pending recovery 元数据\n\n如脚本返回非零退出码，报告错误并停止。\n如脚本返回零退出码，归档完成。\n脚本摘要中的 `X\u002FY steps succeeded` 以真实执行步骤计数，不会因 delta spec 同步或文档标注重复累计。\n\n脚本会调用 OpenSpec 归档能力按 `ADDED\u002FMODIFIED\u002FREMOVED\u002FRENAMED` 语义合并主 spec，并在归档后校验主 spec 中没有残留 delta-only section 标题。\n\n如需预览而不实际执行，使用 `--dry-run` 参数。\n\n### 3. 生命周期闭环\n\nSpec 生命周期在此完成：\n```\nbrainstorming → delta spec → 实施 → 验证 → 主 spec 合并 → design doc 标注 → 归档\n```\n\n### 4. 提交归档改动\n\n归档脚本只移动文件和合并 spec，不会自动提交。归档完成后工作区会有以下未提交改动：\n- change 目录从 `openspec\u002Fchanges\u002F\u003Cname>\u002F` 移动到 `openspec\u002Fchanges\u002Farchive\u002FYYYY-MM-DD-\u003Cname>\u002F`\n- 主 spec 按 delta 语义合并的内容\n- design doc \u002F plan 的归档元数据标注\n\n**必须提示用户提交这些归档改动**，否则归档成果会停留在工作区。展示待提交文件后建议执行：\n\n```bash\ngit add -A\ngit commit -m \"chore: archive \u003Cchange-name>\"\n```\n\n如分支处理（阶段 4）选择尚未合并到主分支，提交后按所选方式（合并 \u002F PR \u002F 保持分支）一并收尾。\n\n## 退出条件\n\n- 归档脚本执行成功（退出码 0）\n- 归档目录 `openspec\u002Fchanges\u002Farchive\u002FYYYY-MM-DD-\u003Cchange-name>\u002F` 存在\n- 归档后的 `.comet.yaml` 中 `archived: true`\n\n归档脚本会把 `openspec\u002Fchanges\u002F\u003Cname>\u002F` 移动到 `openspec\u002Fchanges\u002Farchive\u002FYYYY-MM-DD-\u003Cname>\u002F`。\n\n> **WARNING**: 归档成功后**不要再对原 change 名运行** `node \"$COMET_GUARD\" \u003Cchange-name> archive`，因为原活跃目录已经不存在。误调会导致 guard 报错\"change directory not found\"。归档完整性以脚本退出码和归档目录状态为准。\n\n## 完成\n\nComet 流程全部完成。如需开始新工作，调用 `\u002Fcomet` 或 `\u002Fcomet-open`。\n\n## 上下文压缩恢复\n\n按 `comet\u002Freference\u002Fcontext-recovery.md` 执行，phase 参数为 `archive`。若 `archived: true` 且归档目录存在，归档已完成，无需再次执行归档操作。\n","# Comet 阶段 5：归档（Archive）\n\n## 前置条件\n\n- 验证已通过（阶段 4 完成）\n- 分支已处理\n- `openspec\u002Fchanges\u002F\u003Cname>\u002F.comet.yaml` 中 `verify_result: pass`\n\n## 步骤\n\n### 0. 输出语言约束\n\n归档摘要和生命周期闭环说明必须使用触发本次工作流的用户请求语言。\n\n### 0b. 入口状态验证（Entry Check）\n\n按 `comet\u002Freference\u002Fscripts.md` 定位脚本（定位 `comet-env.mjs`），然后执行入口验证；从任意入口恢复时先按 `comet\u002Freference\u002Fcontext-recovery.md` 运行恢复检查：\n\n```bash\nnode \"$COMET_STATE\" check \u003Cname> archive\n```\n\n验证通过后继续 Step 1。验证失败时脚本会输出具体失败原因。\n\n### 1. 归档前最终确认（阻塞点）\n\n入口验证通过后，**必须按 `comet\u002Freference\u002Fdecision-point.md` 的协议暂停并等待用户确认是否立即归档**。不得在用户确认前运行 `node \"$COMET_ARCHIVE\" \"\u003Cchange-name>\"`。\n\n确认前必须向用户展示简短摘要：\n- change 名称\n- 验证报告路径和结论\n- 分支处理状态\n- 本次归档将执行的不可逆动作：按 OpenSpec delta 语义合并主 spec、标注 design doc \u002F plan、移动 change 到 archive 目录\n\n用户确认问题必须以单选题形式呈现，包含以下选项：\n- 「确认归档」— 立即执行归档脚本，完成 spec 合并和 change 移动\n- 「需要调整或重新验证」— 不执行归档；运行 `node \"$COMET_STATE\" transition \u003Cchange-name> archive-reopen` 回到 `phase: verify`，再调用 `\u002Fcomet-verify`。若验证阶段确认需要修复，再按 `\u002Fcomet-verify` 的验证失败决策回到 `\u002Fcomet-build`\n- 「暂不归档」— 不执行归档，保留当前 `phase: archive` 状态，等待用户稍后再次调用 `\u002Fcomet-archive`\n\n只有用户选择「确认归档」后，才允许继续 Step 2。用户选择「需要调整或重新验证」后，必须先执行 `archive-reopen` 状态回退，不得手动编辑 `.comet.yaml`。\n\n### 2. 执行归档\n\n运行归档脚本，自动完成以下全部步骤：\n\n```bash\nnode \"$COMET_ARCHIVE\" \"\u003Cchange-name>\"\n```\n\n脚本自动执行：\n1. 入口状态验证（phase=archive, verify_result=pass, archived=false）\n2. Design doc 前置元数据标注（archived-with, status）\n3. Plan 前置元数据标注（archived-with）\n4. 调用 OpenSpec archive 按 delta 语义合并主 spec 并移动 change 到归档目录\n5. 校验主 spec 未残留 delta-only section 标题\n6. 在 OpenSpec 实际归档目录中更新 archived 状态，并协调 pending recovery 元数据\n\n如脚本返回非零退出码，报告错误并停止。\n如脚本返回零退出码，归档完成。\n脚本摘要中的 `X\u002FY steps succeeded` 以真实执行步骤计数，不会因 delta spec 同步或文档标注重复累计。\n\n脚本会调用 OpenSpec 归档能力按 `ADDED\u002FMODIFIED\u002FREMOVED\u002FRENAMED` 语义合并主 spec，并在归档后校验主 spec 中没有残留 delta-only section 标题。\n\n如需预览而不实际执行，使用 `--dry-run` 参数。\n\n### 3. 生命周期闭环\n\nSpec 生命周期在此完成：\n```\nbrainstorming → delta spec → 实施 → 验证 → 主 spec 合并 → design doc 标注 → 归档\n```\n\n### 4. 提交归档改动\n\n归档脚本只移动文件和合并 spec，不会自动提交。归档完成后工作区会有以下未提交改动：\n- change 目录从 `openspec\u002Fchanges\u002F\u003Cname>\u002F` 移动到 `openspec\u002Fchanges\u002Farchive\u002FYYYY-MM-DD-\u003Cname>\u002F`\n- 主 spec 按 delta 语义合并的内容\n- design doc \u002F plan 的归档元数据标注\n\n**必须提示用户提交这些归档改动**，否则归档成果会停留在工作区。展示待提交文件后建议执行：\n\n```bash\ngit add -A\ngit commit -m \"chore: archive \u003Cchange-name>\"\n```\n\n如分支处理（阶段 4）选择尚未合并到主分支，提交后按所选方式（合并 \u002F PR \u002F 保持分支）一并收尾。\n\n## 退出条件\n\n- 归档脚本执行成功（退出码 0）\n- 归档目录 `openspec\u002Fchanges\u002Farchive\u002FYYYY-MM-DD-\u003Cchange-name>\u002F` 存在\n- 归档后的 `.comet.yaml` 中 `archived: true`\n\n归档脚本会把 `openspec\u002Fchanges\u002F\u003Cname>\u002F` 移动到 `openspec\u002Fchanges\u002Farchive\u002FYYYY-MM-DD-\u003Cname>\u002F`。\n\n> **WARNING**: 归档成功后**不要再对原 change 名运行** `node \"$COMET_GUARD\" \u003Cchange-name> archive`，因为原活跃目录已经不存在。误调会导致 guard 报错\"change directory not found\"。归档完整性以脚本退出码和归档目录状态为准。\n\n## 完成\n\nComet 流程全部完成。如需开始新工作，调用 `\u002Fcomet` 或 `\u002Fcomet-open`。\n\n## 上下文压缩恢复\n\n按 `comet\u002Freference\u002Fcontext-recovery.md` 执行，phase 参数为 `archive`。若 `archived: true` 且归档目录存在，归档已完成，无需再次执行归档操作。\n",{"name":5,"description":7},"master","a61a2e5b4766e1ad62377dec598e402560a259b6","eval\u002Flocal\u002Fskills\u002Fbenchmarks\u002F040-beta\u002Fcomet-archive",314,"https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet","https:\u002F\u002Fdocs.comet.rpamis.com","https:\u002F\u002Fgithub.com\u002Frpamis","More Efficient, Easier to Use, and Less Annoying","2026-11-15 00:26:58",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add rpamis\u002Fcomet --skill comet-archive",{"tool":38,"command":39},"bunx","bunx skills add rpamis\u002Fcomet --skill comet-archive",{"tool":41,"command":42},"pnpm","pnpm dlx skills add rpamis\u002Fcomet --skill comet-archive","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Feval\u002Flocal\u002Fskills\u002Fbenchmarks\u002F040-beta\u002Fcomet-archive\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":18},"01M72W3K6F0C2FKZ8DHABM49R7","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Feval\u002Flocal\u002Fskills\u002Fbenchmarks\u002Fdependency\u002Fsuperpowers\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M72W3HCPQ3GVMACX61QJTD4B","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Feval\u002Flocal\u002Fskills\u002Fbenchmarks\u002Fdependency\u002Fsuperpowers\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M72W3F8EVD3EK4NXJG40P84K","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Feval\u002Flocal\u002Fskills\u002Fbenchmarks\u002Fdependency\u002Fsuperpowers\u002Fverification-before-completion\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M72W3CA9YM0Y6CSXXTNCV1CA","using-git-worktrees","Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback","https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Feval\u002Flocal\u002Fskills\u002Fbenchmarks\u002Fdependency\u002Fsuperpowers\u002Fusing-git-worktrees\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M72W3AEH0F548GTPRNYRR3H3","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Feval\u002Flocal\u002Fskills\u002Fbenchmarks\u002Fdependency\u002Fsuperpowers\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M72W38EN8NEKX1YN4W9G19Y2","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Feval\u002Flocal\u002Fskills\u002Fbenchmarks\u002Fdependency\u002Fsuperpowers\u002Fsystematic-debugging\u002FSKILL.md",[],[]]