github-pr

github-pr is a command for Claude Code from restarter/lets-workflow. It costs 20 tokens per session (11,020 once invoked), scanned C, original, MIT.

A command for reviewing GitHub pull requests, which are proposed code changes shared for team review. It covers reading the changes, discussing findings, posting inline comments, checking fixes, and approving or requesting changes.

In plain words
What is it for?
Use it to review a pull request, resume a saved review, check whether requested fixes were made, or help an author handle and respond to review comments.
Why use it?
It keeps the review work in one guided process instead of making you track comments, fixes, and approval steps separately. It requires the GitHub CLI (`gh`) to be installed and signed in.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: names the AskUserQuestion tool; mentions Claude Code.

Part of the lets plugin — 20 skills, 26 commands, 16 agents shipped together

Good fit Use it to review a pull request, resume a saved review, check whether requested fixes were made, or help an author handle and respond to review comments.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/restarter/lets-workflow/github-pr
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/restarter/lets-workflow

Made for: Claude Code.

Or install lets, the plugin that ships this one along with the rest of its 20 skills, 26 commands, 16 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for github-pr

README.md
[![agentmods](https://agentmods.dev/badge/commands/restarter/lets-workflow/github-pr/github.svg)](https://agentmods.dev/commands/restarter/lets-workflow/github-pr)
Your own site
<a href="https://agentmods.dev/commands/restarter/lets-workflow/github-pr"><img src="https://agentmods.dev/badge/commands/restarter/lets-workflow/github-pr/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for github-pr

Your own site · 80×15
<a href="https://agentmods.dev/commands/restarter/lets-workflow/github-pr"><img src="https://agentmods.dev/badge/commands/restarter/lets-workflow/github-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 11,020 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00020 $0.11020
Opus 5.5 $0.00008 $0.04408
Sonnet 5.5 $0.00004 $0.02204
Haiku 4.5 $0.00002 $0.01102

Measured 19d ago against content hash bbe7a1473d24, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

github-pr scanned grade C with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 19d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

1. Delete PR folder: `rm -rf "$PR_DIR"` (removes state + all temp files)
plugins/lets/commands/github-pr.md · 1,233 lines

How it starts

The opening of the file, as written. The whole thing — 1,233 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitHub PR Review Lifecycle

Full GitHub PR review lifecycle: analyze code, discuss findings with user, post inline comments, follow-up on fixes, approve or request changes.

GitHub only (the full posting lifecycle). This command drives inline comments / follow-up / approve / merge exclusively via the gh CLI. For Bitbucket, /lets:review <PR> already reviews a PR end to end (fetch + diff + discussion + summary post via bbb); only the inline/approve/merge lifecycle here stays GitHub-only for now. LETS_PR_FLOW=local users finish tasks via /lets:done.

Requires: gh CLI installed and authenticated.

IMPORTANT: If the spec below invokes any deferred tool (e.g. AskUserQuestion), you MUST load and call it as specified. Never skip the call, never substitute a default answer of your own — the tool invocation is part of the contract. This is critical.

Usage

/lets:github-pr <PR-url-or-number>     # Start new review
/lets:github-pr                        # Resume from saved state
/lets:github-pr --follow-up            # Check if fixes addressed comments
/lets:github-pr --respond [PR]         # Author: triage review comments, fix, reply
/lets:github-pr --approve              # Approve PR
/lets:github-pr --merge                # Merge PR
/lets:github-pr --status               # Show current review state
/lets:github-pr --cancel               # Clean up state, abandon review

Step 1: Detect Mode

Verify gh CLI

gh auth status 2>&1 || echo "gh not authenticated"

If gh not available or not authenticated, stop: "gh CLI required. Run gh auth login."

Parse argument

Interpret user intent:

  • PR URL or number -> extract PR number
  • --follow-up -> Phase 3
  • --respond -> Phase R (author respond)
  • --approve -> Phase 4
  • --merge -> merge only
  • --status -> show state and exit
  • --cancel -> clean up state and exit
  • No argument, no flag -> check for existing state files

Check for existing state

LETS_PROJECT_ROOT=$(git rev-parse --show-toplevel)
PR_DIR="$LETS_PROJECT_ROOT/.lets/execution/pr-{number}"
STATE_FILE="$PR_DIR/review.json"

Read the full file on GitHub · 1,233 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 19d ago Changed · +2 lines bbe7a1473d24
  2. 20d ago Changed · +2 lines 0aa09e291300
  3. 23d ago Changed · +3 lines 720a2b86bed9
  4. 1mo ago First seen · 1,226 lines · 20 tokens per session scan C 5429a77e2668

Subscribe to this mod's changes

github-pr is a command published in the GitHub repository restarter/lets-workflow (17 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 11,020 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.