comet-verify

Name: comet-verify
Availability: InStock
Author: rpamis

Verify development changes align with designs before branch archival.

2.7k|259|Updated May 14, 2026

Search Tags:#verification #build #verify #code-review #branch-management #comet

Ready to run

npx skills add https://github.com/rpamis/comet --skill comet-verify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: comet-verify
Source: https://github.com/rpamis/comet/tree/main/assets/skills/comet-verify
Command: npx skills add https://github.com/rpamis/comet --skill comet-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that final verification confirms implementation aligns with the design and that the development branch is ready for closure and archival.

Core Features & Use Cases

Enforces cross-artifact verification (tasks, design, delta specs, tests) before archiving.
Guides decision points for fixing deviations or accepting risks, ensuring traceability.
Orchestrates finalization steps with guard and finishing phases to complete the cycle.

Quick Start

Run the /comet-verify command to kickoff the verification and closure process for the current change.

Frequently Asked Questions about comet-verify

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

FAQPage Schema

How do I verify development changes align with design specs before archiving a branch?▼

You can verify development changes against defined designs by running a cross-artifact verification process that checks tasks, design specs, delta specs, and tests before archiving the branch.

What is the process for closing and archiving a development branch in Comet?▼

Branch closure and archival involves a finalization phase that confirms implementation aligns with design, handles the development branch properly, and generates a verification report to complete the cycle.

How do I handle deviations found during final build verification?▼

During final build verification, you can handle deviations by using guided decision points to either fix the deviations or accept the risks, ensuring full traceability before proceeding to archival.

Do I need access to the Comet environment to run verification and closure steps?▼

Yes, you need access to the Comet environment and its skill tools to run verification checks, generate verification reports, and update the state for the current change.

What artifact checks are required during the build and finishing phase?▼

The build and finishing phase requires cross-artifact checks across tasks, design documents, delta specs, and tests to confirm implementation aligns with the defined design before final archival.

When should I run verification reporting for ongoing development changes?▼

Verification reporting should be run during Phase 4 after build and finishing steps, applying artifact checks and decision points to confirm the development branch is ready for closure and archival.