acceptance-verification

Verify GitHub issue acceptance criteria against codebase evidence.

11|1|Updated Feb 9, 2026

Search Tags:#quality assurance #github #acceptance criteria #project board #issue verification #code evidence #epic verification

Ready to run

npx skills add https://github.com/mindcockpit-ai/cognitive-core --skill acceptance-verification

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: acceptance-verification
Source: https://github.com/mindcockpit-ai/cognitive-core/tree/main/core/skills/acceptance-verification
Command: npx skills add https://github.com/mindcockpit-ai/cognitive-core --skill acceptance-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the risk of prematurely closing GitHub issues by automatically verifying if acceptance criteria are fully met, preventing overlooked gaps in development work.

Core Features & Use Cases

Criteria Extraction and Assessment: Parses issue bodies for criteria and evaluates them as PASS, PARTIAL, FAIL, or N/A based on codebase evidence.
Evidence Gathering and Reporting: Searches commits, code, tests, and docs for proof, then posts detailed verification comments with summaries and recommendations.
Use Case: During a sprint review, invoke this on issue #42 to check if all requirements for a new feature are implemented, auto-tick passed checkboxes, and block closure if any criteria fail.

Quick Start

Invoke the acceptance-verification skill on GitHub issue number 42 to check if its criteria are met and post a verification summary.

Frequently Asked Questions about acceptance-verification

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

FAQPage Schema

How do I automatically verify GitHub issue acceptance criteria against codebase evidence?▼

Automatically verifying GitHub issue acceptance criteria involves parsing issue bodies and evaluating them as PASS, PARTIAL, FAIL, or N/A based on commits, code changes, tests, and documentation. The skill posts detailed verification comments with summaries and recommendations.

What is the best way to prevent prematurely closing GitHub issues during sprint reviews?▼

Preventing premature GitHub issue closure during sprint reviews requires a closure guard that checks if all acceptance criteria are fully met. The skill applies this guard, auto-ticks passed checkboxes, and blocks resolution if any criteria fail.

Can I check if epic requirements are fully implemented before resolving issues in my project board?▼

Yes, you can check if epic requirements are fully implemented by verifying acceptance criteria against codebase evidence. The skill searches commits, code, tests, and docs for proof, ensuring complete implementation before issue resolution.

Does acceptance verification work with GitHub project boards for quality assurance?▼

Acceptance verification works with GitHub project boards for quality assurance by evaluating issue criteria and posting structured reports. It integrates directly into software development workflows for sprint reviews and epic management.

What are the limitations of using automated criteria extraction for issue verification?▼

Automated criteria extraction for issue verification relies on parsing issue bodies and searching codebase evidence. If issue acceptance criteria are vaguely defined or code commits lack clear references, the evaluation may result in PARTIAL or FAIL statuses.

How do I extract and assess issue acceptance criteria for structured reporting?▼

Extracting and assessing issue acceptance criteria requires parsing issue bodies and searching commits, code, tests, and docs for evidence. The skill evaluates each criterion and posts a structured verification comment with a summary and recommendations.