cu-verify

Scan documentation and codebase artifacts to verify implementation completeness for specified use cases.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/cfardev/ayv-comercial --skill cu-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cu-verify
Source: https://github.com/cfardev/ayv-comercial/tree/main/.agents/skills/cu-verify
Command: npx skills add https://github.com/cfardev/ayv-comercial --skill cu-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

It simplifies the process of verifying whether all technical implementation tasks for a use case are completed, reducing manual review time.

Core Features & Use Cases

  • Implementation Auditing: Checks codebase for evidence of database models, API endpoints, and frontend components related to specific use cases.
  • Progress Tracking: Identifies gaps in implementation by comparing documented checklists with actual code artifacts.
  • Use Case: A developer wants to confirm if all aspects of a new feature are implemented before merging the branch, saving time during code review.

Quick Start

Provide the CU number or ask "which CU to verify" and the skill will scan relevant docs and code to check implementation status.

Frequently Asked Questions about cu-verify

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

FAQPage Schema
How do I verify implementation completeness for specific use cases before a code review?

To verify use case implementation completeness, scan documentation and codebase artifacts to check that all technical checkboxes like database models, API endpoints, and frontend components are present and fully implemented.

What is the best way to check if all technical tasks for a new feature are implemented before merging?

The best way to check implementation status before merging is auditing the codebase for evidence of required components, comparing documented checklists against actual code artifacts to identify any incomplete technical gaps.

Can I track use case implementation progress by comparing documented checklists with codebase artifacts?

Yes, you can track implementation progress by comparing documented checklists with actual code artifacts, which identifies gaps in database models, API endpoints, and frontend components to ensure all use case tasks are completed.

Does implementation auditing work for identifying gaps in database models and API endpoints?

Implementation auditing works for identifying gaps by scanning the codebase for evidence of database models, API endpoints, and frontend components, ensuring all specified use case technical requirements are checked off.

How do I check off technical checkboxes for a use case by scanning the codebase?

You check off technical checkboxes by scanning the codebase and documentation for specific use case evidence, verifying that required implementations like API endpoints and frontend components exist and are complete.

Why do I need to scan both documentation and code artifacts for implementation verification?

Scanning both documentation and code artifacts is needed for implementation verification because it cross-references documented checklists against actual codebase evidence, accurately identifying gaps and preventing incomplete use case merges.