check-pr

Inspect GitHub, GitLab, or Perforce changes for review comments, failing checks, and description gaps.

Updated Jun 16, 2026

Search Tags:#code review #pull request #github #gitlab #perforce #ci checks #greptile

One-click install

npx skills add https://github.com/adamtpang/summon.company --skill check-pr-adamtpang

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: check-pr
Source: https://github.com/adamtpang/summon.company/tree/main/.agents/skills/check-pr
Command: npx skills add https://github.com/adamtpang/summon.company --skill check-pr-adamtpang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Reviewing a pull request, merge request, or Perforce changelist means manually checking CI status, reading every inline and general comment, verifying bot reviews are current, and confirming the description is complete. This Skill automates that inspection and helps fix and resolve the issues it finds. ## Core Features & Use Cases - Multi-platform change inspection: Detects GitHub, GitLab, or Perforce automatically and fetches PR/MR/CL details, status checks, review comments, and discussions via gh, glab, or p4 CLIs. - Fresh Greptile review gating: Blocks completion unless a Greptile review is tied to the exact current head SHA, treating stale or failed reviews as blockers. - Issue triage and resolution: Categorizes findings as actionable, informational, or already addressed, applies fixes on request, and resolves review threads via GraphQL or the GitLab discussions API. - Use Case: After pushing a commit to an existing GitHub PR, ask the agent to check the PR; it waits for pending checks, verifies a fresh Greptile pass on the new head, summarizes reviewer feedback, fixes actionable comments, pushes, and resolves the threads. ## Quick Start Ask the agent to check the current branch's pull request for review comments and failing checks, then fix any actionable issues it finds.

Frequently Asked Questions about check-pr

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

FAQPage Schema

How do I check a GitHub PR for review comments and failing checks?▼

Run the check-pr workflow, which uses gh pr view and the GitHub API to fetch status checks, inline review comments, and general issue comments. It waits for pending checks to finish, then reports actionable and informational findings in a summary table.

How do I check a GitLab merge request for unresolved discussions?▼

The workflow uses glab api to fetch MR discussions, filtering for notes of type DiffNote with resolved set to false. It also checks pipeline status and can resolve each discussion individually with a PUT request, since GitLab has no batch resolution.

Does this work with Perforce changelists?▼

Yes, it detects Perforce via p4 info or a .p4config file and inspects pending or shelved changelists using p4 describe, p4 diff2, and p4 review. Since Perforce lacks native CI checks and thread resolution, it relies on external review tools like Swarm for those steps.

Why does the check block even though Greptile already reviewed my PR?▼

A Greptile review only counts if it is tied to the PR's exact current head SHA. After pushing a new commit, older reviews are stale, so the workflow blocks until a fresh Greptile check completes with a success or neutral conclusion on the new head.

What tools are required to run this PR check workflow?▼

It requires git plus the platform CLI: gh for GitHub, glab for GitLab, or p4 for Perforce, each installed and authenticated. jq is also used to parse JSON responses from the API calls.