nicolas-codemate/pr-info

PR Info Skill

Fetches comprehensive PR information from GitHub, handling repo detection and all comment sources automatically.

<context> Direct `gh` commands often fail because: - Claude hardcodes wrong `owner/repo` in API paths (404 errors) - `--jq` returns exit code 1 on empty results - Inline review comments require a separate API endpoint from PR reviews - Three distinct comment sources must be combined for a complete picture

This skill solves all of these by using a tested wrapper script. </context>

<instructions>

Quick Usage (preferred)

Run the helper script from the project directory:

# Basic: overview + reviews + all comments
~/.claude/scripts/gh-pr-info.sh <PR_NUMBER>

# With diff included
~/.claude/scripts/gh-pr-info.sh <PR_NUMBER> --diff

# From a different repo path
~/.claude/scripts/gh-pr-info.sh <PR_NUMBER> --repo-path /path/to/repo

The script auto-detects owner/repo from the current git context. No need to hardcode repository paths.

Manual Commands (when script is unavailable)

If you need to run individual commands, always detect the repo first:

# Step 1: detect repo (MANDATORY before any gh api call)
REPO=$(gh repo view --json nameWithOwner -q .nameWithOwner)

# Step 2: use $REPO in API paths
gh api "repos/$REPO/pulls/<N>/reviews" --paginate
gh api "repos/$REPO/pulls/<N>/comments" --paginate    # inline comments
gh api "repos/$REPO/issues/<N>/comments" --paginate    # conversation comments

Three Comment Sources

| Endpoint | What it contains | |----------|-----------------| | pulls/<N>/reviews | Review verdicts (APPROVED, CHANGES_REQUESTED, COMMENTED) with optional body | | pulls/<N>/comments | Inline comments on specific code lines (path + line number) | | issues/<N>/comments | General conversation comments on the PR discussion tab |

</instructions> <constraints> - NEVER hardcode `owner/repo` in API paths — always detect via `gh repo view` - NEVER use `gh pr view --json comments,reviews --jq '...'` alone — it misses inline comments - ALWAYS check all three comment sources for complete feedback - When the script is available, prefer it over manual commands </constraints>