prp-verify

Automate verification of GitHub pull requests against acceptance criteria.

2|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/gobikom/prp-framework --skill prp-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prp-verify
Source: https://github.com/gobikom/prp-framework/tree/main/adapters/codex/prp-verify
Command: npx skills add https://github.com/gobikom/prp-framework --skill prp-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github-api, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the verification of Pull Requests (PRs) to ensure that they meet the defined acceptance criteria, reducing manual review time and improving code quality.

Core Features & Use Cases

  • Automated Verification: Automatically checks PRs against their acceptance criteria.
  • Evidence Reporting: Provides detailed evidence for each criterion, including PASS/FAIL/PARTIAL verdicts.
  • Use Case: Before merging a PR, use this Skill to verify that all acceptance criteria have been met, ensuring that the code change aligns with the intended functionality.

Quick Start

Run the prp-verify skill with the PR number: prp-verify 42

Frequently Asked Questions about prp-verify

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

FAQPage Schema
How do I automatically verify GitHub pull requests against acceptance criteria before merging?

You can automatically verify pull requests against acceptance criteria by running the prp-verify skill with a PR number. It analyzes PR diffs to ensure all criteria are met and returns detailed evidence with PASS, FAIL, or PARTIAL verdicts.

What is automated PR verification and how does it evaluate code changes?

Automated PR verification evaluates code changes by analyzing PR diffs against predefined acceptance criteria. It provides detailed evidence for each requirement, assigning PASS, FAIL, or PARTIAL verdicts to ensure code changes align with intended functionality.

Do I need GitHub API access to check if my pull requests meet requirements?

Yes, you need GitHub API access to check if your pull requests meet requirements. The verification process depends on the github-api dependency to retrieve PR data and analyze diffs against their defined acceptance criteria.

How do I get PASS, FAIL, or PARTIAL evidence reports for my GitHub PRs?

To get PASS, FAIL, or PARTIAL evidence reports for GitHub PRs, run the automated verification process on the target PR. It analyzes the code diff and generates detailed evidence showing exactly which acceptance criteria were met or failed.

Can I use automated PR verification to reduce manual code review time on GitHub?

Yes, you can use automated PR verification to reduce manual code review time on GitHub. By automatically checking PRs against defined acceptance criteria, it ensures code quality and confirms that intended functionality is met before merging.