pr

Inspect GitHub pull request metadata, diffs, checks, and comments read-only.

29|1|Updated Jul 18, 2015

Search Tags:#github #analysis #pr #code-review #read-only #reviews

Ready to run

npx skills add https://github.com/joshmanders/dotfiles --skill pr-joshmanders

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly understand the purpose, changes, and review context of a GitHub pull request using only read operations, enabling safe evaluation without altering any state.

Core Features & Use Cases

Read-only PR view: fetches metadata, body, base/head refs, and files changed to provide a clear PR snapshot.
Diff & checks: retrieves the full diff and CI/check status to assess impact and quality.
Use Case: triage PRs efficiently to decide whether further discussion or action is needed, without submitting reviews or comments.

Quick Start

Provide a PR reference to start an in-depth, read-only PR analysis.

Frequently Asked Questions about pr

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

FAQPage Schema

How do I review a GitHub pull request without modifying the repository state?▼

Review a GitHub pull request without modifying state by performing read-only operations to fetch metadata, diffs, and checks. This method preserves repository integrity by avoiding comments, reviews, or state-changing actions during code analysis.

What is read-only PR analysis and when do I need it?▼

Read-only PR analysis is the process of assessing a pull request's purpose and changes without write access. You need it when triaging PRs to understand impact and CI check status safely before deciding if further action is required.

Can I retrieve CI check status and file diffs for a pull request using only read operations?▼

Yes, you can retrieve CI check status and full file diffs using only read operations. This fetches the head and base refs along with changed files to provide a clear snapshot for evaluating code quality and impact.

How do I triage GitHub pull requests efficiently to decide if they need further discussion?▼

Triage GitHub pull requests efficiently by retrieving the PR body, metadata, and full diff to understand the review context. This read-only approach provides a clear snapshot to decide if further discussion is needed without submitting comments.

Are there limitations to analyzing GitHub pull requests without submitting reviews or comments?▼

The limitation of analyzing GitHub pull requests without submitting reviews is that you cannot approve, request changes, or leave inline comments. It is strictly for safe evaluation and retrieval of metadata and diffs while preserving repository integrity.