check-pr

Review GitHub pull requests against policy gates and CI signals.

8|4|Updated Jan 15, 2026

Search Tags:#ci/cd #code review #pull request #github #policy #readiness

Ready to run

npx skills add https://github.com/jscraik/Agent-Skills --skill check-pr-jscraik

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: check-pr
Source: https://github.com/jscraik/Agent-Skills/tree/main/github/greptile/check-pr
Command: npx skills add https://github.com/jscraik/Agent-Skills --skill check-pr-jscraik

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the review of GitHub pull requests, ensuring they meet policy and readiness standards before merging, and helps verify Greptile setup prerequisites.

Core Features & Use Cases

Policy-Gated Review: Runs a comprehensive readiness review including status checks, review comments, and governance policies.
Setup Verification: Verifies Greptile setup and policy prerequisites for a repository.
Use Case: Before merging a critical feature, use this Skill to get a clear, prioritized summary of all outstanding checks, comments, and policy blockers, ensuring no merge is made until all gates are passed.

Quick Start

Run check-pr on this branch and tell me what still blocks merge.

Frequently Asked Questions about check-pr

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

FAQPage Schema

How do I check if a GitHub pull request is ready to merge?▼

To check if a GitHub pull request is ready to merge, you can run a policy-gated review that evaluates status checks, unresolved review comments, and CI signals to provide a prioritized remediation plan.

What does policy-gated code review evaluate before merging?▼

Policy-gated code review evaluates GitHub pull request readiness by assessing status checks, unresolved review comments, CI signals, and governance policies to identify any blockers before merging.

Do I need Greptile and GitHub CLI to review pull request readiness?▼

Yes, you need GitHub CLI to provide repository context and Greptile access to retrieve the review data required to assess pull request readiness and verify setup prerequisites.

What's the best way to find unresolved blockers in a pull request?▼

The best way to find unresolved blockers in a pull request is to run an automated readiness review that generates a prioritized remediation plan covering status checks and review comments.

Can I verify Greptile setup prerequisites for a repository before reviewing PRs?▼

Yes, you can verify Greptile setup and policy prerequisites for a repository to ensure the environment is correctly configured before performing policy-gated pull request reviews.