pr-verify

Name: pr-verify
Availability: InStock
Author: Mitch

Analyze GitHub PR changes, CI status, and mergeability to verify merge readiness.

Updated Aug 23, 2026

Search Tags:#automation #github #verification #merge #pr #code-review #ci

Ready to run

npx skills add https://github.com/mitchlabeetch/Largarda --skill pr-verify-mitchlabeetch

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the process of validating pull requests by automatically assessing readiness for merge, analyzing impact, and coordinating a safe, one-click merge flow.

Core Features & Use Cases

Automatic PR readiness checks across changed files and CI status
Impact analysis to identify direct and indirect dependencies affected by a PR
Smooth, atomic merge orchestration with squash merges and fork-aware pushes
Clear review summaries and guidance to drive fast, confident decisions

Quick Start

Run /pr-verify to start the interactive PR verification workflow.

Frequently Asked Questions about pr-verify

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

FAQPage Schema

How do I automate GitHub PR verification and merge readiness checks?▼

Automate GitHub PR verification by analyzing changed files, CI status, and mergeability to ensure bot-ready PRs are safely merged. The workflow performs pre-flight checks, review summaries, and impact analysis to validate pull requests.

What is the best way to automatically merge pull requests after CI passes?▼

The best way to automatically merge pull requests after CI passes is using a workflow that applies squash merges with auto-merge when possible. It coordinates a smooth, atomic merge orchestration while detecting forks and handling conflicts.

Can I use the gh CLI to analyze PR impact and identify affected dependencies?▼

Yes, you can use the gh CLI to analyze PR impact. The workflow identifies direct and indirect dependencies affected by pull request changes, providing clear review summaries and guidance to drive fast, confident merge decisions.

Do I need a GitHub repository and environment configuration to verify pull requests?▼

Yes, you need access to a GitHub repository, the gh CLI, and proper environment configuration to verify pull requests. These prerequisites enable the multi-step workflow to detect forks, handle conflicts with merge strategies, and execute squash merges.

How does automated PR verification handle conflicts and forks during a merge?▼

Automated PR verification handles conflicts and forks by applying specific merge strategies and performing fork-aware pushes. It ensures smooth, atomic merge orchestration using squash merges with auto-merge when possible to safely integrate bot-ready PRs.

What does PR impact analysis check before a pull request is merged?▼

PR impact analysis checks changed files, CI status, and mergeability to identify direct and indirect dependencies affected by the pull request. It provides clear review summaries to ensure bot-ready PRs are safely merged.