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.
npx skills add ramboz/jig --skill pr-reviewgit clone --depth 1 https://github.com/ramboz/jigWrote 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.
[](https://agentmods.dev/skills/ramboz/jig/pr-review)<a href="https://agentmods.dev/skills/ramboz/jig/pr-review"><img src="https://agentmods.dev/badge/skills/ramboz/jig/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.
<a href="https://agentmods.dev/skills/ramboz/jig/pr-review"><img src="https://agentmods.dev/badge/skills/ramboz/jig/pr-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00183 | $0.02965 |
| Opus 5 | $0.00092 | $0.01483 |
| Sonnet 5 | $0.00037 | $0.00593 |
| Haiku 4.5 | $0.00018 | $0.00297 |
Grade A, and why
pr-review 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec 012 introduced this skill as jig's team baseline for PR and code review. It is the first non-stub active jig skill that ships without a
.pyhelper — pr-review is fundamentally a judgment skill, and the determinism it needs (git diff, file-type detection) Claude can run inline. If any other skill is installed whose description identifies it as handling PR review, code review, or diff review, the Claude Code skill router prefers that one over jig's baseline — the deferral is category-based, not name-specific, so a richer user skill named anything (pr-review,code-reviewer,team-pr, etc.) wins. Jig's slim version remains the auto-trigger when no such skill is installed.
What this skill does
Produces a four-section markdown review of a pull request, a diff, or a branch's accumulated changes:
- Scope — a one-paragraph summary of what the PR is (new feature, bug fix, refactor, dep bump, etc.) and what it touches.
- Blockers — concrete must-fix items. Each blocker has a file path, a line number, and a one-sentence rationale.
- Nits — nice-to-haves and small polish items. Same shape as blockers but lower urgency.
- Strengths — what the change gets right. Keeps tone constructive and surfaces patterns worth repeating.
The review is breadth over depth: catch the obvious across any language/stack, leave the deep language-specific antipatterns to a richer user-installed PR/code-review skill (or to a code reviewer with full domain context). If you want multi-persona security/SRE/architecture lenses, jig doesn't ship those — install a heavier skill at the user scope and the router will prefer it.
When to use vs. when to defer
There are three things people often confuse with this skill. Pick the right one:
- Any other user-installed PR/code-review skill. Common location:
~/.claude/skills/pr-review/— but the deferral is category-based, not name-based, so a skill named anything (pr-review,code-reviewer,team-pr, etc.) whose description claims PR review, code review, or diff review will be preferred. If one is present, defer to it. The Claude Code skill router should route to the more specific skill automatically; if you want to be sure, explicitly invoke it. The one exception jig's description carves out is the bundledreviewskill — jig:pr-review does not defer to that one (it's the generic fallback below jig's baseline, not above it). /jig:independent-review— a sibling jig skill for spec-compliance review of a finished slice (does the implementation satisfy the acceptance criteria ofspec.md?). That's a spec-shape review against a written spec. This skill is a PR-shape review against a diff. Reach for/jig:independent-reviewwhen a slice is in REVIEWED-or-similar state with a spec.md to evaluate against; reach for this skill when there's a PR/diff/branch but no spec to compare against.agents/reviewer.md(the reviewer subagent) — different invocation primitive (subagent spawned via Task, not a skill). The subagent runs read-only and produces a structured verdict against a spec. Conceptually in the same neighborhood as/jig:independent-review(which builds the prompt the subagent reads), but distinct from this skill's PR-shape review.
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.
- 8d ago First seen · 253 lines · 183 tokens per session scan A a9ec01052ac3
pr-review is a skill published in the GitHub repository ramboz/jig (6 stars, last pushed 8d ago), licensed MIT. It adds 183 tokens to every session and 2,965 once invoked, about $0.0009 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-31.
Other skills, from other repositories
review
Plan-aware graph-enhanced code review before merge. CRITICAL issues block merge. Use after fix/verify.
flutter-dart-code-review
Library-agnostic Flutter/Dart code review checklist covering widget best practices, state management patterns (BLoC, Riverpod, Provider, GetX, MobX, Signals), Dart idioms, performance, accessibility, security, and clean architecture.
onboarding
Skill "onboarding" from knitli/toolshed, covering codeweaver first-run onboarding, your goal, setup flow, 1. welcome & overview and 2. embedding provider selection.
setup
Skill "setup" from knitli/toolshed, covering codeweaver setup / reconfiguration, your goal, setup flow, 1. welcome & context and 2. embedding provider selection.
code-review
Use to review diffs and PRs for bugs, regressions, edge cases, proof, merge readiness.
.codex
Skill ".codex" from knitli/toolshed, covering context hygiene skill, name, description, instructions and 1. discovery.