comet-verify

Verifies Comet changes, records evidence, and manages repair loops.

Updated Aug 5, 2026
One-click install
npx skills add https://github.com/JhonMA82/api-starter --skill comet-verify-jhonma82
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comet-verify
Source: https://github.com/JhonMA82/api-starter/tree/main/.opencode/skills/comet-verify
Command: npx skills add https://github.com/JhonMA82/api-starter --skill comet-verify-jhonma82

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It enforces a structured verification phase for Comet-managed changes, ensuring completed work is checked against tasks, specs, and design docs before archiving, with evidence recorded and repair loops handled automatically. ## Core Features & Use Cases - Scale-based verification: Automatically assesses change size and runs either a lightweight 6-point check or a full verification against delta specs and design documents. - Automatic repair loops: Returns to the build phase for up to three repairable failures, classifying findings as CRITICAL, IMPORTANT, WARNING, or SUGGESTION, and escalating to user decisions after the retry limit. - Evidence recording and phase guard: Writes a verification report, records it in .comet.yaml, and transitions to the archive phase only after the guard passes. - Use Case: After finishing implementation of a multi-file change, run the verify phase to confirm tasks are complete, tests pass, specs match, and produce an auditable verification report before archiving. ## Quick Start Invoke /comet-verify after the build phase completes to verify the current Comet change and record its verification evidence.

Frequently Asked Questions about comet-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a Comet change after the build phase?▼

Run the verify phase by selecting the change with comet state select, then comet state check <name> verify. The skill assesses scale, runs lightweight or full checks, records a verification report, and transitions to the archive phase via the guard.

What is the difference between light and full verification mode?▼

Light mode runs 6 checks including tasks completion, build, tests, and security for small changes. Full mode applies when tasks exceed 3, delta specs span more than one capability, or more than 8 files change, adding spec coverage and design doc consistency checks.

What happens when verification fails in Comet?▼

Repairable failures automatically return to the build phase via comet state transition verify-fail, up to three consecutive times. After the retry limit, the user must choose to continue fixing or stop the workflow; CRITICAL and IMPORTANT findings are never waivable.

How does Comet handle spec drift during verification?▼

When delta specs contradict the design doc, verification pauses and asks the user to choose: append an Implementation Divergence section, return to build to update the design doc, or accept the deviation and continue.

Can I override the automatic verify mode assessment?▼

Yes. Run comet state set <change-name> verify_mode light or full at any time to override the automated scale assessment before or during verification.