pr-verify

Automate PR verification by analyzing PR bodies, comments, linked issues, and CI status.

1.8k|247|Updated Feb 16, 2026

Search Tags:#automation #verification #pr #e2e-testing #ci #pull-request

Ready to run

npx skills add https://github.com/phodal/routa --skill pr-verify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-verify
Source: https://github.com/phodal/routa/tree/main/.claude/skills/pr-verify
Command: npx skills add https://github.com/phodal/routa --skill pr-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR workflows often stall on manual checks of PR bodies, linked issues, screenshots, CI status, and end-to-end readiness. This skill automates the verification process to ensure consistency and accelerate safe merges.

Core Features & Use Cases

Requirements analysis: extracts acceptance criteria, linked issues, screenshots/videos, and breaking changes from PR bodies.
Comment synthesis & review: summarizes reviewer notes and categorizes statuses (Resolved, Pending, Blocking).
CI & E2E readiness: validates CI checks and can orchestrate optional end-to-end testing.

Quick Start

Run the pr-verify skill on a target PR to generate a comprehensive verification report.

Frequently Asked Questions about pr-verify

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

FAQPage Schema

How do I automate pull request verification for CI-driven repositories?▼

You automate pull request verification by running a skill that analyzes PR bodies, linked issues, comments, and CI status to determine merge readiness. It applies structured phases including requirements analysis and CI checks to ensure consistency and accelerate safe merges.

What is PR verification and how does it check merge readiness?▼

PR verification is the process of validating that a pull request meets all requirements before merging. It works by extracting acceptance criteria from the PR body, synthesizing reviewer comments, and validating CI status to categorize issues as Resolved, Pending, or Blocking.

Can I orchestrate end-to-end testing as part of my PR verification workflow?▼

Yes, you can orchestrate optional end-to-end testing during PR verification. The workflow validates CI checks and can trigger E2E testing readiness to ensure the pull request is fully verified before proceeding to a safe merge.

How do I extract acceptance criteria and breaking changes from a PR body?▼

You extract acceptance criteria and breaking changes by running automated requirements analysis on the PR body. This process scans the pull request text to identify linked issues, screenshots, videos, and breaking changes to ensure all merge requirements are documented.

What is the best way to synthesize code review comments for pending issues?▼

The best way to synthesize code review comments is through automated comment synthesis, which summarizes reviewer notes and categorizes their statuses into Resolved, Pending, or Blocking to clarify what prevents a safe merge.

Do I need existing CI checks to use automated PR verification?▼

Existing CI checks are validated as part of the PR verification process to determine merge readiness. The workflow analyzes your CI status alongside PR bodies and review comments, meaning your repository should be CI-driven to get the full verification report.