Verified:GitHub

check-pr

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

Updated Mar 26, 2026

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

One-click install

npx skills add https://github.com/nabitllc/todero --skill check-pr-nabitllc

Or copy as Structured Prompt for Agent▼

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

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 review comment, verifying the description is complete, and confirming bot reviews are fresh for the current head commit. 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, inline comments, and general discussion via gh, glab, or p4 CLIs. - Fresh review gating: Polls pending status checks and blocks completion until a Greptile review tied to the exact current head SHA concludes cleanly, preventing stale approvals. - 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 CI, verifies a fresh Greptile pass on the new head, summarizes reviewer feedback, fixes actionable comments, pushes, and resolves the threads. ## Quick Start Check the PR for my current branch and fix any actionable review comments.

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, categorizes each finding as actionable or informational, and can fix and push changes on request.

How do I check a GitLab merge request from the command line?▼

The workflow detects GitLab from the git remote and uses glab mr view plus the discussions API to fetch MR details, pipelines, and comments. It polls pipelines until none are running or pending, then reports findings and can resolve discussions individually via PUT requests.

Does this work with Perforce changelists?▼

Yes, it detects Perforce via p4 info or P4 environment variables and inspects pending or shelved changelists using p4 describe, p4 diff2, and p4 review. Since Perforce lacks native CI checks and thread resolution, it validates the CL description and re-shelves fixes instead.

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 and concluded with success or neutral. Reviews on older commits are stale after a new push, so the workflow blocks and suggests triggering a fresh review with a comment like "@greptile review".

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

You need git plus the platform CLI installed and authenticated: gh for GitHub, glab for GitLab, or p4 for Perforce. The workflow auto-detects the platform, and self-hosted GitLab instances can be forced with the --vcs gitlab flag.