verify-ac

Automate machine verification of GitHub issue acceptance criteria against code.

13|3|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/phrazzld/agent-skills --skill verify-ac
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-ac
Source: https://github.com/phrazzld/agent-skills/tree/main/core/verify-ac
Command: npx skills add https://github.com/phrazzld/agent-skills --skill verify-ac

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the verification of acceptance criteria against code implementation, ensuring that software meets specified requirements before commits or merges.

Core Features & Use Cases

  • Automated AC Verification: Machine-verifies acceptance criteria from GitHub issues.
  • Strategy Selection: Intelligently selects the best verification strategy (test, command, behavioral) based on AC semantics and diff context.
  • Hard Gate Policy: Enforces a strict policy, failing the process if any AC remains unverified after retries.
  • Use Case: When working on a feature, run this skill to automatically confirm that the implemented code satisfies all the acceptance criteria listed in the associated GitHub issue, preventing regressions and ensuring quality.

Quick Start

Use the verify-ac skill to machine-verify the acceptance criteria for issue number 123.

Frequently Asked Questions about verify-ac

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

FAQPage Schema
How do I automate acceptance criteria verification against my code implementation?

Automated acceptance criteria verification selects the best strategy per criterion, such as test, command, or behavioral checks, to evaluate code implementation against GitHub issue requirements before merges.

Do I need the GitHub CLI to verify issue acceptance criteria?

Yes, verifying acceptance criteria requires the gh CLI for GitHub issue data retrieval and rg for file searching to evaluate code implementation against specified requirements.

How does automated verification handle unverified acceptance criteria?

Automated verification enforces a strict hard gate policy, failing the process if any acceptance criteria remain unverified after automated retries to prevent regressions and ensure quality.

What is the best way to gate commits against GitHub issue acceptance criteria?

Gating commits against acceptance criteria is handled by machine-verifying requirements through intelligent strategy selection based on AC semantics and diff context, functioning seamlessly from autopilot, pr-fix, and pr-polish workflows.

When do I need machine verification for acceptance criteria?

Machine verification is needed when working on a feature to automatically confirm implemented code satisfies all acceptance criteria listed in an associated GitHub issue, preventing regressions before commits or merges.