comet-verify

Name: comet-verify
Availability: InStock
Author: zhentingwu-wzt

Automate code verification against design specifications and project requirements.

6|Updated May 25, 2026

Search Tags:#automation #devops #quality assurance #code review #verification #branch management

Ready to run

npx skills add https://github.com/zhentingWu-wzt/wgenty-code --skill comet-verify-zhentingwu-wzt

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: comet-verify
Source: https://github.com/zhentingWu-wzt/wgenty-code/tree/main/.wgenty-code/skills/comet-verify
Command: npx skills add https://github.com/zhentingWu-wzt/wgenty-code --skill comet-verify-zhentingwu-wzt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the critical gap between code implementation and production readiness by automating the verification of design consistency, test coverage, and branch cleanup.

Core Features & Use Cases

Automated Verification: Executes multi-stage validation checks including build verification, test execution, and security scanning.
Design Alignment: Ensures code changes strictly adhere to established design documents and technical specifications.
Branch Lifecycle Management: Orchestrates the safe merging, pushing, or archiving of development branches with built-in guardrails.
Use Case: After completing a complex feature, use this skill to verify that your implementation matches the design spec and safely transition the branch to the archive phase.

Quick Start

Trigger the comet-verify skill to initiate the final validation and closure process for your current development branch.

Frequently Asked Questions about comet-verify

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

FAQPage Schema

How do I automate code verification against design specifications before merging?▼

Automated code verification against design specifications is handled through multi-stage validation checks. This process ensures code changes strictly adhere to established design documents and technical specifications before pushing or merging development branches.

What is the best way to manage development branch closure and repository cleanup?▼

Development branch closure and repository cleanup is orchestrated through safe merging, pushing, or archiving. This approach uses built-in guardrails to safely transition completed branches to the archive phase after verifying production readiness.

Can I run security scanning and build verification as part of automated branch validation?▼

Yes, security scanning and build verification can be run as part of automated branch validation. The process executes multi-stage validation checks to satisfy technical requirements for build integrity and security compliance.

How does automated design alignment check for consistency with technical requirements?▼

Automated design alignment checks for consistency by verifying code implementation against project requirements and established design documents. This ensures the completed implementation matches the intended technical specifications before closure.

Do I need to manually trigger branch lifecycle management after completing a feature?▼

You can trigger the branch lifecycle management process to initiate final validation and closure. This automates the transition of your current development branch through verification, safe merging, and archiving without manual repository cleanup.