check-acceptance-criteria

Verify acceptance-criteria checkboxes in GitHub pull requests against repository code.

3|1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/auerbachb/claude-code-config --skill check-acceptance-criteria
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-acceptance-criteria
Source: https://github.com/auerbachb/claude-code-config/tree/main/.claude/skills/check-acceptance-criteria
Command: npx skills add https://github.com/auerbachb/claude-code-config --skill check-acceptance-criteria

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the tedious and error-prone manual verification of Test Plan acceptance-criteria checkboxes in pull requests, ensuring PRs meet documented requirements before merge.

Core Features & Use Cases

  • Automated Verification: Parses the PR body to extract acceptance-criteria checkboxes, inspects relevant source files, and determines whether each unchecked criterion is satisfied by the code.
  • Safe, Idempotent Updates: Checks off only the criteria that have been programmatically verified and updates the PR body via the GitHub CLI while surfacing script and GH errors explicitly.
  • Reporting and Triage: Produces a concise summary of total, passed, failed, and manual-test items to guide reviewers and developers.
  • Use Case: Integrate into pre-merge checks to automatically validate implementation against documented acceptance criteria and reduce manual review overhead.

Quick Start

Run the skill to verify acceptance criteria for the current branch's pull request.

Frequently Asked Questions about check-acceptance-criteria

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

FAQPage Schema
How do I automatically verify pull request acceptance criteria checkboxes?

You can automatically verify pull request acceptance criteria by running a script that parses the PR body, evaluates unchecked criteria against relevant source files, and uses the GitHub CLI to tick passing checkboxes. It updates the PR body directly.

How does automated acceptance criteria verification work with the GitHub CLI?

Automated acceptance criteria verification works by using the GitHub CLI to parse the PR body, evaluate unchecked criteria against relevant source files, and update the PR body by ticking programmatically verified checkboxes while reporting failures.

Do I need jq and gh installed to automate PR test plan checks?

Yes, you need both the GitHub CLI (gh) and jq installed to automate PR test plan checks. These dependencies are required to parse PR body data and interact with your repository to verify and update acceptance criteria.

What is the best way to validate a Test Plan section in a GitHub PR before merge?

The best way to validate a Test Plan section before merge is to integrate an automated verification script into your pre-merge checks. It inspects source files to determine if criteria are satisfied and updates the PR body accordingly.

Can I use this automated PR verification for manual-test items?

You can use this PR verification to identify manual-test items. The script produces a concise summary reporting total, passed, failed, and manual-test items, but only checks off criteria that have been programmatically verified.

Why are my automated PR acceptance criteria checks failing to update the body?

Automated PR acceptance criteria checks fail to update the body when script or GitHub CLI errors occur. The script surfaces these errors explicitly and only performs safe, idempotent updates for criteria it can programmatically verify.