[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72W04MCQ56V3MW0FXCX0KW6":3,"skill-same:01M72W04MCQ56V3MW0FXCX0KW6":56},{"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},"01M72W04MCQ56V3MW0FXCX0KW6","comet-verify",null,"Verify a Classic change and record the results. Use when the user invokes \u002Fcomet-verify or Classic Runtime enters Verify.","rpamis\u002Fcomet","rpamis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F153429891?v=4","01M72VXBR7EQYMM7KN8C19244V","01M72VXBRYC06QG0ZH0JBGV09V",3298,"MIT","https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fcomet-verify\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: comet-verify\ndescription: 'Verify a Classic change and record the results. Use when the user invokes \u002Fcomet-verify or Classic Runtime enters Verify.'\n---\n\n# Comet Phase 4: Verify\n\nOn first entering a phase, handing off to a new Agent, or restoring context, read and follow [Task Context and Artifact Language](..\u002Fcomet-classic\u002Freference\u002Fscripts.md#task-context-and-artifact-language). Prefer the current continuation or claimed Action's `contextRequest`; do not retrieve repeatedly during uninterrupted work in the same phase.\n\nAfter entry returns layout, follow the [shared phase entry](..\u002Fcomet-classic\u002Freference\u002Fscripts.md#shared-phase-entry) when receiving a phase for the first time or when its binding changes. Reuse the valid [layout](..\u002Fcomet-classic\u002Freference\u002Fclassic-layout.md); do not run an extra root show first. When edits require judgement, load edit continuation through the shared entry.\n\n## SDK Run path\n\nFirst follow [ordinary commands and checks](..\u002Fcomet\u002Freference\u002Fplatform-execution.md). New and upgraded Runs use platform tools and submit actual reports to the original Run. Automatic upgrades do not restore old check executors. Phase preparation, user choices, task completion, and acceptance requirements remain in force.\n\nOn first entering the current SDK phase, handing off to a new Agent, or restoring context, read [phase entry and recovery](..\u002Fcomet-classic\u002Freference\u002Fsdk-methods.md#phase-entry-and-recovery) and the current phase's section in that reference. Reuse them when already available and still valid in this session. Continue with the phase below; recovery routes based on `nextAction.kind` apply only to older responses without a continuation mode.\n\nReuse the latest valid response for the same change, workspace, and Run: `agent.continuation`, `data.nextAction`, phase, revision, and path summaries. Run `comet state next \u003Cchange-name> --json` only for cold recovery, workspace or external state changes, a stale response version, or missing information needed for the current step; loading the next Skill is not a reason to query again. Runtime still validates current versions and evidence on writes; cached context cannot bypass checks or approval. Confirm `data.runtimeFormat: sdk`, `data.phase: verify`, and `nextAction.kind`, and work in the bound `projectRoot`. Run `comet classic workspace resolve \u003Cchange-name> --json` only when paths are missing or the binding has changed; use `comet state check \u003Cchange-name> verify --json` only when current task, workspace, or evidence summaries are missing. For `reconcile`, use `comet state check \u003Cchange-name> verify --recover --json` to investigate the original Action and check; stop if its result remains unknown.\n\n1. Follow the risk assessment, integrated review, and light\u002Ffull verification methods in SDK execution methods, but use the SDK Run as evidence authority. Do not call legacy `state scale`, `state set`, `comet handoff`, or `comet check` evidence commands. For implementation or task defects, report the specific failure. Only when `\u003Cprofile>.verify.run` is pending (`\u003Cprofile>` is full, hotfix, or tweak), run `comet state transition \u003Cchange-name> verify-fail --reason \"\u003Cfailure-reason>\"`. It records a failed Verify Action and returns to Build. Follow the current Build Action from that response; query `state next --json` only if continuation information is missing. Investigate existing failed or unknown checks before reporting another failure.\n2. After acceptance succeeds, save actual checks, evidence references, review conclusions, and acceptable deviations in `\u003Creport-ref>`. Submit `comet guard \u003Cchange-name> verify --report \u003Creport-ref> --apply --checks \u003Cchecks-json-file>`. Guard validates this Run’s report and acceptance requirements without repeating commands. For failures or unknown results, inspect the original task using the returned Action; read `state next --json` only if continuation is missing. Do not interpret failure as success.\n\n3. After Guard succeeds, use that response directly; run `comet state next \u003Cchange-name> --json` only if phase or nextAction is missing. Load `\u002Fcomet-archive` only when phase is Archive and `nextAction.kind` points there. Verify passing does not itself authorize Archive; obtain the current delivery decision there.\n\n## Compat path\n\nThe remaining original Runtime steps apply only to `runtimeFormat: compat`. Read [Compat operations](reference\u002Fcompat.md) and continue its current phase. SDK does not load that reference.\n\n## Optional change walkthrough\n\nAt Build completion and before presenting Verify results, check the project `.comet\u002Fconfig.yaml` field `change_walkthrough` (enabled by default; only explicit `false` disables it). When enabled, read and execute [Change walkthrough](..\u002Fcomet\u002Freference\u002Fchange-walkthrough.md), use the shared template to generate or update the same `walkthrough.html`, and provide an opening link. When disabled, skip extra explanation, detailed instructions and rendering; retain the existing summary. Archive preserves existing pages with the materials and links to their actual archived location; it does not generate missing pages, add confirmation or rerun code checks for page updates.\n","# Comet Phase 4: Verify\n\nOn first entering a phase, handing off to a new Agent, or restoring context, read and follow [Task Context and Artifact Language](..\u002Fcomet-classic\u002Freference\u002Fscripts.md#task-context-and-artifact-language). Prefer the current continuation or claimed Action's `contextRequest`; do not retrieve repeatedly during uninterrupted work in the same phase.\n\nAfter entry returns layout, follow the [shared phase entry](..\u002Fcomet-classic\u002Freference\u002Fscripts.md#shared-phase-entry) when receiving a phase for the first time or when its binding changes. Reuse the valid [layout](..\u002Fcomet-classic\u002Freference\u002Fclassic-layout.md); do not run an extra root show first. When edits require judgement, load edit continuation through the shared entry.\n\n## SDK Run path\n\nFirst follow [ordinary commands and checks](..\u002Fcomet\u002Freference\u002Fplatform-execution.md). New and upgraded Runs use platform tools and submit actual reports to the original Run. Automatic upgrades do not restore old check executors. Phase preparation, user choices, task completion, and acceptance requirements remain in force.\n\nOn first entering the current SDK phase, handing off to a new Agent, or restoring context, read [phase entry and recovery](..\u002Fcomet-classic\u002Freference\u002Fsdk-methods.md#phase-entry-and-recovery) and the current phase's section in that reference. Reuse them when already available and still valid in this session. Continue with the phase below; recovery routes based on `nextAction.kind` apply only to older responses without a continuation mode.\n\nReuse the latest valid response for the same change, workspace, and Run: `agent.continuation`, `data.nextAction`, phase, revision, and path summaries. Run `comet state next \u003Cchange-name> --json` only for cold recovery, workspace or external state changes, a stale response version, or missing information needed for the current step; loading the next Skill is not a reason to query again. Runtime still validates current versions and evidence on writes; cached context cannot bypass checks or approval. Confirm `data.runtimeFormat: sdk`, `data.phase: verify`, and `nextAction.kind`, and work in the bound `projectRoot`. Run `comet classic workspace resolve \u003Cchange-name> --json` only when paths are missing or the binding has changed; use `comet state check \u003Cchange-name> verify --json` only when current task, workspace, or evidence summaries are missing. For `reconcile`, use `comet state check \u003Cchange-name> verify --recover --json` to investigate the original Action and check; stop if its result remains unknown.\n\n1. Follow the risk assessment, integrated review, and light\u002Ffull verification methods in SDK execution methods, but use the SDK Run as evidence authority. Do not call legacy `state scale`, `state set`, `comet handoff`, or `comet check` evidence commands. For implementation or task defects, report the specific failure. Only when `\u003Cprofile>.verify.run` is pending (`\u003Cprofile>` is full, hotfix, or tweak), run `comet state transition \u003Cchange-name> verify-fail --reason \"\u003Cfailure-reason>\"`. It records a failed Verify Action and returns to Build. Follow the current Build Action from that response; query `state next --json` only if continuation information is missing. Investigate existing failed or unknown checks before reporting another failure.\n2. After acceptance succeeds, save actual checks, evidence references, review conclusions, and acceptable deviations in `\u003Creport-ref>`. Submit `comet guard \u003Cchange-name> verify --report \u003Creport-ref> --apply --checks \u003Cchecks-json-file>`. Guard validates this Run’s report and acceptance requirements without repeating commands. For failures or unknown results, inspect the original task using the returned Action; read `state next --json` only if continuation is missing. Do not interpret failure as success.\n\n3. After Guard succeeds, use that response directly; run `comet state next \u003Cchange-name> --json` only if phase or nextAction is missing. Load `\u002Fcomet-archive` only when phase is Archive and `nextAction.kind` points there. Verify passing does not itself authorize Archive; obtain the current delivery decision there.\n\n## Compat path\n\nThe remaining original Runtime steps apply only to `runtimeFormat: compat`. Read [Compat operations](reference\u002Fcompat.md) and continue its current phase. SDK does not load that reference.\n\n## Optional change walkthrough\n\nAt Build completion and before presenting Verify results, check the project `.comet\u002Fconfig.yaml` field `change_walkthrough` (enabled by default; only explicit `false` disables it). When enabled, read and execute [Change walkthrough](..\u002Fcomet\u002Freference\u002Fchange-walkthrough.md), use the shared template to generate or update the same `walkthrough.html`, and provide an opening link. When disabled, skip extra explanation, detailed instructions and rendering; retain the existing summary. Archive preserves existing pages with the materials and links to their actual archived location; it does not generate missing pages, add confirmation or rerun code checks for page updates.\n",{"name":5,"description":7},"master","9b2c15a8cbb321ae4e36d48849676e14d90eba24","assets\u002Fskills\u002Fcomet-verify",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-verify",{"tool":38,"command":39},"bunx","bunx skills add rpamis\u002Fcomet --skill comet-verify",{"tool":41,"command":42},"pnpm","pnpm dlx skills add rpamis\u002Fcomet --skill comet-verify","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fcomet-verify\u002FSKILL.md",true,[46,52],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",176,"https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fcomet-verify\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"reference\u002Fcompat.md",15634,"https:\u002F\u002Fgithub.com\u002Frpamis\u002Fcomet\u002Fblob\u002Fmaster\u002Fassets\u002Fskills\u002Fcomet-verify\u002Freference\u002Fcompat.md",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"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":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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",[],[]]