agentmods.dev

Review a GitHub PR (via gh)

Review a GitHub PR (via gh) is a skill for Claude Code, Codex from AuraVixStudio/caelo. It costs 48 tokens per session (572 once invoked), scanned A, original, Apache-2.0.

A review workflow for a GitHub pull request, which is a proposed set of code changes awaiting review. It uses the gh command-line tool or GitHub integration to examine changes and gather findings.

In plain words
What is it for?
Use it to fetch a pull request, inspect its diff, ask focused reviewers for file-and-line findings, combine the results, and optionally post the review.
Why use it?
It organizes review across changed areas so correctness, security, and maintainability issues are easier to spot.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

not rated 24repo +2 27d ago A scan 48 tokens original Apache-2.0

Good fit Use it to fetch a pull request, inspect its diff, ask focused reviewers for file-and-line findings, combine the results, and optionally post the review.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/auravixstudio/caelo/pr-review
View source ↗ AuraVixStudio/caelo auravixstudio.github.io
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.

Any agent
npx skills add AuraVixStudio/caelo --skill pr-review
Clone the repo
git clone --depth 1 https://github.com/AuraVixStudio/caelo

Made for: Claude Code, Codex.

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 Review a GitHub PR (via gh)

README.md
[![agentmods](https://agentmods.dev/badge/skills/auravixstudio/caelo/pr-review/github.svg)](https://agentmods.dev/skills/auravixstudio/caelo/pr-review)
Your own site
<a href="https://agentmods.dev/skills/auravixstudio/caelo/pr-review"><img src="https://agentmods.dev/badge/skills/auravixstudio/caelo/pr-review/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 Review a GitHub PR (via gh)

Your own site · 80×15
<a href="https://agentmods.dev/skills/auravixstudio/caelo/pr-review"><img src="https://agentmods.dev/badge/skills/auravixstudio/caelo/pr-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 572 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00048 $0.00572
Opus 5 $0.00024 $0.00286
Sonnet 5 $0.00010 $0.00114
Haiku 4.5 $0.00005 $0.00057

Measured 9d ago against content hash ff591fafdf2c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

Review a GitHub PR (via gh) scanned grade A with 0 findings 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 9d 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

caelo_core/skills/builtin/pr-review/SKILL.md · 39 lines

What it actually says

Review a GitHub PR (via gh)

Use this to review a specific GitHub pull request thoroughly and — only if asked — post the review back to GitHub. (For a review of the local changes, use the review skill; to drive a PR to green CI, use pr-babysit.)

Dependency: needs the gh CLI installed + authenticated (run gh auth login), or the GitHub MCP server enabled. If neither is available, tell the user and stop. Note: run_command runs with a scrubbed environment, so env tokens like GH_TOKEN/GITHUB_TOKEN are stripped — gh must be authenticated via gh auth login (its config/keyring), not an env var.

Steps

  1. Fetch the PR. With run_command: gh pr view <n> --json title,body,headRefName,baseRefName,files and gh pr diff <n> (or the GitHub MCP tools). Identify the changed files and group them by area.
  2. Delegate reviewers. delegate a reviewer per area (parallel for independent areas). Give each reviewer the exact files plus the relevant diff hunks, and ask for correctness bugs, security issues, and quality/maintainability concerns — each with a file:line reference and a short rationale. Reviewers are READONLY (no run_command).
  3. Consolidate. Merge the returned findings, drop duplicates, and sort by severity.
  4. Report. Present one prioritized list (most severe first) to the user.
  5. Post (only if asked). If the user explicitly wants the review posted, use gh pr review <n> --comment (or --request-changes / --approve) with the consolidated summary as the body. This is a MUTATION and goes through approval. Do NOT merge or close the PR.

Notes

  • Reviewers do not run commands — gather the gh pr diff output yourself and pass the relevant hunks into each subagent's task.
  • Keep each reviewer's scope tight so its summary stays concrete and actionable.
  • Never post to GitHub without an explicit request from the user.
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. 9d ago First seen · 39 lines · 48 tokens per session scan A ff591fafdf2c

Subscribe to this mod's changes

Review a GitHub PR (via gh) is a skill published in the GitHub repository AuraVixStudio/caelo (24 stars, last pushed 27d ago), licensed Apache-2.0. It adds 48 tokens to every session and 572 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code reviewai-agentbyokcoding-agentdesktop-appelectronfastapi
Related

Other skills, from other repositories

api-reviewer

Use when the user asks to review or change an HTTP, RPC, event, CLI, or SDK API contract. Inspect routes, schemas, authorization, errors, compatibility, and consumers before editing, then verify request and response behavior with focused tests.

lfyxhappy/lfcode · 53 tokens

code-reviewer

A code-review guide for examining a change and its surrounding behavior for bugs, regressions, security risks, compatibility problems, and missing tests. A code review checks proposed changes before they are accepted.

lfyxhappy/lfcode · 82 tokens

pull-request-author

Use when the user asks to prepare, update, audit, or submit a pull request. Inspect repository contribution rules, branch state, diff, tests, and the target base first; create a focused reviewable change description and do not commit, push, or open a hosted pull request without explicit authorization.

lfyxhappy/lfcode · 64 tokens

refactor-engineer

Use when the user requests a behavior-preserving code refactor, cleanup, extraction, consolidation, or architectural simplification. Map all references and contracts before editing, keep the change scoped, and prove behavior with focused tests and type checks.

lfyxhappy/lfcode · 52 tokens

agentbro-pr-merge

Use when reviewing, fixing CI for, approving workflows for, or merging AgentBro pull requests into dev/main, especially external contributor PRs where contributor attribution matters.

shirenchuang/agentbro · 38 tokens

code-reviewer

Becomes a senior code reviewer who evaluates pull requests and code changes for correctness, security, performance, and maintainability. Use when the user asks for code review, PR feedback, code quality assessment, or merge readiness evaluation. Do NOT use when writing new code, debugging runtime errors, designing…

FerroxLabs/wayland · 75 tokens