React Router PR Finish Line
remix-run/react-router
Takes a blocked community pull request in React Router and adds the missing tests, change file or docs so it can merge, working on the contributor's branch.
Diff-based PR review across code quality, test coverage, silent failures, type design, and comment quality with severity-ranked findings.
Install PR Review
$ npx skills add Mathews-Tom/armory --skill pr-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Mathews-Tom/armory pr-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Mathews-Tom/armory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pr-review .claude/skills/pr-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pr-review" agent skill from https://github.com/Mathews-Tom/armory/tree/main/skills/pr-review into .claude/skills/pr-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Mathews-Tom/armory/tree/main/skills/pr-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Mathews-Tom/armory --skill pr-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Mathews-Tom/armory pr-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Mathews-Tom/armory.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/pr-review .agents/skills/pr-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pr-review" agent skill from https://github.com/Mathews-Tom/armory/tree/main/skills/pr-review into .agents/skills/pr-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Mathews-Tom/armory --skill pr-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Mathews-Tom/armory pr-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Mathews-Tom/armory.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/pr-review .cursor/skills/pr-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pr-review" agent skill from https://github.com/Mathews-Tom/armory/tree/main/skills/pr-review into .cursor/skills/pr-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Mathews-Tom/armory.git --path skills/pr-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Mathews-Tom/armory --skill pr-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Mathews-Tom/armory pr-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Mathews-Tom/armory.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/pr-review .gemini/skills/pr-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pr-review" agent skill from https://github.com/Mathews-Tom/armory/tree/main/skills/pr-review into .gemini/skills/pr-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Mathews-Tom/armory pr-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Mathews-Tom/armory --skill pr-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Mathews-Tom/armory.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/pr-review .github/skills/pr-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pr-review" agent skill from https://github.com/Mathews-Tom/armory/tree/main/skills/pr-review into .github/skills/pr-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Mathews-Tom/armory --skill pr-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Mathews-Tom/armory pr-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Mathews-Tom/armory.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/pr-review .opencode/skills/pr-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pr-review" agent skill from https://github.com/Mathews-Tom/armory/tree/main/skills/pr-review into .opencode/skills/pr-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pr-review- GitHub stars
- 329
- Token cost
- ~2.6k tokens
- SKILL.md length
- 1,006 words
- Files
- 8 (incl. references)
- Skills in repo
- 80
- Repo updated
- First seen
- Licence
- MIT
At a glance
Diff-based PR review across code quality, test coverage, silent failures, type design, and comment quality with severity-ranked findings.
- Works in 4 steps: Scope → Route → Review → …
- Review this code
- SKILL.md covers Reference Files, Workflow, Output Format and Aspect Selection, plus 5 more sections
- Calls git and gh
What it does
PR Review is an agent skill from Mathews-Tom/armory. Diff-based PR review across code quality, test coverage, silent failures, type design, and comment quality with severity-ranked findings. Triggers on: "review my PR", "review this code", "check my changes", "audit this PR", "code review". NOT for pre-landing gate, use pre-landing-review.
Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `evals/cases.yaml`, `references/code-review.md` and `references/comment-quality.md`).
It sits in Development, covering Pull requests, Test coverage and Code quality. It works with Git. The repository describes itself as: Curated, production-grade skills for AI coding agents. Battle-tested workflows for developers who use AI seriously. The licence is MIT.
When your agent uses it
- Review this code
- Check my changes
Example prompts
- “review my PR”
- “review this code”
- “check my changes”
- “/pr-review”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 4594fb7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitgh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
PR Review loads about 2.6k tokens when it runs, and up to ~6k if it reads all its reference files. Until then it costs about 75 tokens; SKILL.md has 1,006 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Mathews-Tom/armory at commit 4594fb7, republished under its MIT licence (© Mathews-Tom). 1,006 words, ~2,593 tokens.
Download SKILL.mdSave it as
.claude/skills/pr-review/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.- name
- pr-review
- description
- Diff-based PR review across code quality, test coverage, silent failures, type design, and comment quality with severity-ranked findings. Triggers on: "review my PR", "review this code", "check my changes", "audit this PR", "code review". NOT for pre-landing gate, use pre-landing-review.
- metadata.version
- 1.1.1
- metadata.category
- review
- metadata.tags
- code-review, pull-request, quality, diff-analysis
- metadata.difficulty
- intermediate
- metadata.phase
- review
PR Review
Diff-based code review across five dimensions. Reads the changed files, selects applicable review methodologies, and produces an aggregated report with severity-ranked findings.
Native alternative: Claude Code's
/ultrareviewruns a lightweight native bug-focused review (three free per month on Pro/Max plans at Opus 4.7's launch). Use this skill for five-dimension severity-ranked analysis (code quality + tests + error handling + types + comments) with file:line references; use/ultrareviewfor a quick bug-hunting pass on a diff.
Reference Files
| File | Contents | Load When |
|---|---|---|
references/code-review.md | Guideline compliance, bug detection, confidence scoring | Always |
references/test-analysis.md | Behavioral test coverage, criticality rating | Test files changed |
references/error-handling.md | Silent failure patterns, catch block analysis | Error handling changed |
references/type-design.md | Invariant analysis, 4-dimension rating rubric | Type definitions added/modified |
references/comment-quality.md | Comment accuracy, long-term value, rot detection | Comments/docstrings added |
Workflow
Phase 1: Scope
- Determine the review target:
- Default:
git diff(unstaged changes) - If user specifies a PR:
git diff main...HEADorgh pr diff <number> - If user specifies files: review those files directly
- Default:
- List all changed files with
git diff --name-only - Read the project's CLAUDE.md (if present) for project-specific rules
Phase 2: Route
Classify changed files and select applicable dimensions:
| Condition | Dimension | Reference to Load |
|---|---|---|
| Always | Code review | references/code-review.md |
Files matching *test*, *spec*, *_test.*, test_* | Test analysis | references/test-analysis.md |
| Files containing try/catch, except, .catch, Result, error callbacks | Error handling | references/error-handling.md |
| Files containing class, interface, type, struct, enum, dataclass definitions | Type design | references/type-design.md |
| Files with new/modified docstrings, JSDoc, or block comments | Comment quality | references/comment-quality.md |
Load only the reference files that apply. Skip dimensions with no matching files.
Phase 3: Review
For each applicable dimension, analyze the diff using the loaded methodology:
- Code review — scan every changed file for guideline violations and bugs. Apply confidence scoring (0-100). Only report issues >= 80.
- Test analysis — map test coverage to changed code paths. Rate gaps 1-10. Only report gaps >= 5.
- Error handling — examine every error handler in the diff for silent failures. Classify CRITICAL/HIGH/MEDIUM.
- Type design — evaluate new or modified types on 4 dimensions (encapsulation, invariant expression, usefulness, enforcement). Rate each 1-10.
- Comment quality — verify accuracy, assess long-term value, flag comment rot.
Phase 4: Aggregate
Merge all findings into a single report, deduplicated and severity-ranked.
Deduplication rules:
- If two dimensions flag the same file:line, keep the higher-severity finding
- If code-review and error-handling both flag an empty catch block, merge into one finding with the error-handling severity (it's the specialist)
Severity mapping across dimensions:
| Dimension | Maps to Critical | Maps to Important | Maps to Suggestion |
|---|---|---|---|
| Code review | Confidence 90-100 | Confidence 80-89 | — |
| Test analysis | Rating 9-10 | Rating 7-8 | Rating 5-6 |
| Error handling | CRITICAL | HIGH | MEDIUM |
| Type design | Any rating <= 3/10 | Any rating 4-6/10 | Rating 7-8/10 |
| Comment quality | Factually incorrect | Misleading or incomplete | Restates obvious code |
Output Format
# PR Review Summary
**Scope:** [X files changed, Y dimensions applied]
**Dimensions:** [list of active dimensions]
## Critical Issues (must fix before merge)
- **[dimension]** `file:line` — Description. Fix suggestion.
## Important Issues (should fix)
- **[dimension]** `file:line` — Description. Fix suggestion.
## Suggestions (consider)
- **[dimension]** `file:line` — Description.
## Strengths
- What's well-done in this changeset.
## Recommended Action
1. Fix critical issues
2. Address important issues
3. Consider suggestions
4. Re-run review after fixesIf no issues are found at any severity level, confirm the code meets standards with a brief summary of what was reviewed and which dimensions were applied.
Aspect Selection
Users can request specific dimensions instead of running all:
| User Says | Dimensions Applied |
|---|---|
| "review my PR" / "check my changes" | All applicable (default) |
| "review the code" / "check code quality" | Code review only |
| "check the tests" / "is test coverage good" | Test analysis only |
| "check error handling" / "find silent failures" | Error handling only |
| "review the types" / "check type design" | Type design only |
| "check the comments" / "review documentation" | Comment quality only |
When a specific aspect is requested, load only that reference file and skip routing.
Error Handling
| Problem | Resolution |
|---|---|
| No git diff available | Ask user to specify files or scope |
| CLAUDE.md not found | Review against general best practices; note the absence |
| No test files in diff | Skip test analysis dimension; note in output |
| Diff is empty | Report "no changes to review" and stop |
| Diff exceeds context limits | Focus on files the user is most likely to care about; summarize skipped files |
Show full SKILL.md (379 more words)Show less
Calibration Rules
- Precision over recall. A false positive erodes trust in the review. Only report issues at >= 80 confidence (code review) or >= 5 criticality (tests). Silence is better than noise.
- File:line references are mandatory. Every finding must include a specific location. Vague findings ("consider improving error handling") are not actionable.
- Project rules override general rules. If CLAUDE.md says "use arrow functions",
do not flag arrow functions even if conventional style prefers
functiondeclarations. - Deduplication is mandatory. If two dimensions flag the same issue, merge them. Never report the same problem twice.
- Acknowledge strengths. A review that only lists problems is demoralizing. Note what's done well, even briefly.
- Code-refiner handles simplification. This skill reviews and reports. It does not
refactor or simplify — that's the
code-refinerskill's job. Keep the roles separate.
Rationalizations
| Rationalization | Reality |
|---|---|
| "Tests pass, so the code is fine" | Tests are necessary but insufficient — they miss architecture, security, readability, and maintainability concerns |
| "It's a small diff, no real review needed" | Small changes cause most production incidents; a 3-line auth bypass is worse than a 300-line refactor |
| "We'll clean it up later" | Later never comes — the review IS the quality gate before code becomes legacy |
| "The author is senior, I trust them" | Seniority doesn't prevent mistakes; fresh eyes catch what familiarity blinds |
| "I already reviewed similar code recently" | Each diff has unique context — assumptions from past reviews cause missed issues |
| "This is just a refactor, nothing can break" | Refactors change behavior in subtle ways — verify with tests and trace call sites |
Red Flags
- Approving without reading every changed file in full (not just diff hunks)
- No file:line references in findings — vague feedback is not actionable
- Skipping a review dimension because "it looks fine"
- Reporting only style issues while ignoring logic, security, or architecture
- Reviewing generated code (migrations, protobuf stubs) with the same rigor as hand-written code
- Merging findings from different dimensions without deduplication
Verification
- Every changed file read in full, not just diff hunks
- Each review dimension scored: correctness, security, performance, readability, architecture
- Every finding includes a file:line reference
- At least one actionable finding per 100 lines changed, or explicit "no issues found" with justification
- Review summary includes risk level (LOW/MEDIUM/HIGH/CRITICAL) and blocking vs. non-blocking classification
- Strengths acknowledged — review is not 100% negative
© Mathews-Tom, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 7 other files (references) in skills/pr-review of Mathews-Tom/armory.
- SKILL.md
- evals/cases.yaml
- evals/fixtures/buggy_diff.patch
- references/code-review.md
- references/comment-quality.md
- references/error-handling.md
- references/test-analysis.md
- references/type-design.md
Open the folder on GitHubat commit 4594fb7
Compare with similar skills
PR Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| PR Review this skillMathews-Tom/armory | 329 | — | ~2.6k | Automated safety check: Pass | MIT | |
| React Router PR Finish Lineremix-run/react-router | 57k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Code ReviewerYikai-Liao/symusic | 189 | 1 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Code Review with Beads Tasksmaslennikov-ig/claude-code-orchestrator-kit | 260 | — | ~2k | Automated safety check: Pass | Custom licence | |
| Databricks CLI PR Checklistdatabricks/cli | 404 | — | ~1.5k | Automated safety check: Pass | Custom licence | |
| Reviewing Changesbitwarden/ios | 699 | — | ~1.1k | Automated safety check: Pass | GPL-3.0 |
Similar skills
Code Reviewer
Yikai-Liao/symusic
Analyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then…
Code Review with Beads Tasks
maslennikov-ig/claude-code-orchestrator-kit
Reviews staged changes, a branch, a PR or a path for bugs, security gaps and performance issues, then writes an evidence-based report and creates Beads tasks.
- Official
Databricks CLI PR Checklist
databricks/cli
Pre-PR checklist for the Databricks CLI repository: run the same format and lint checks as CI, scrub the diff, fill the PR template concisely and add a changelog entry.
- Official
Reviewing Changes
bitwarden/ios
Performs comprehensive code reviews for Bitwarden iOS projects, verifying architecture compliance, style guidelines, compilation safety, test coverage, and security requirements.
PR Readiness Review
ruby-git/ruby-git
Performs a comprehensive pre-PR readiness review covering tests, code quality, security, and commit conventions.
More from Mathews-Tom/armory
All 80 skills in this repoArchitecture Reviewer
Mathews-Tom/armory
Architecture reviews across 7 dimensions (structural, scalability, enterprise readiness, performance, security, ops, data) with scored reports.
Concept To Image
Mathews-Tom/armory
Turn concepts into static HTML visuals exported as PNG or SVG files via HTML/CSS/SVG.
Watch
Mathews-Tom/armory
A skill your agent uses when analyzing an existing video URL or local recording: "watch this video", "analyze youtube video", "summarize this video", "youtube transcript", "find this moment", "what…
Code Refiner
Mathews-Tom/armory
Deep code simplification and refactoring preserving behavior across Python, Go, TypeScript, Rust.
Concept To Video
Mathews-Tom/armory
Turn concepts into animated explainer videos using Manim (Python) with MP4/GIF output, audio overlay, multi-scene composition.
Decision Map
Mathews-Tom/armory
Maps the unresolved architecture, policy, and scope decisions that must be answered before planning can start: one durable decision ticket per question on the issue tracker, typed and blocker-linked…
Related
Works with
Categories
Questions about PR Review
What does PR Review do?
Diff-based PR review across code quality, test coverage, silent failures, type design, and comment quality with severity-ranked findings. PR Review is an agent skill from Mathews-Tom/armory. Diff-based PR review across code quality, test coverage, silent failures, type design, and comment quality with severity-ranked findings.
When should I use PR Review?
PR Review fits situations like: review this code; check my changes.
How do I install PR Review in Claude Code?
Run `npx skills add Mathews-Tom/armory --skill pr-review -a claude-code`. Or copy the skill folder (skills/pr-review in Mathews-Tom/armory) into .claude/skills/pr-review in your project. Claude Code loads it when a task matches its description.
How do I install PR Review in Codex?
Run `npx skills add Mathews-Tom/armory --skill pr-review -a codex`. Or copy the skill folder (skills/pr-review in Mathews-Tom/armory) into .agents/skills/pr-review in your project. Codex loads it when a task matches its description.
Can I use PR Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Mathews-Tom/armory --skill pr-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pr-review, .gemini/skills/pr-review, .github/skills/pr-review and .opencode/skills/pr-review in your project.
What does PR Review need to run?
Going by SKILL.md and its folder, PR Review needs the command-line tools its instructions call (git and gh).
Does PR Review access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is PR Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does PR Review use?
PR Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does PR Review use?
About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.4k tokens, read only when the agent opens those files.
What are the alternatives to PR Review?
Skills that share tags, products or a category with PR Review: React Router PR Finish Line (remix-run/react-router, 57k stars), Code Reviewer (Yikai-Liao/symusic, 189 stars), Code Review with Beads Tasks (maslennikov-ig/claude-code-orchestrator-kit, 260 stars) and Databricks CLI PR Checklist (databricks/cli, 404 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains PR Review?
Mathews-Tom (a GitHub user) maintains it in Mathews-Tom/armory, which has 329 GitHub stars. The repository holds 80 skills in this directory. The repository was last updated on October 6, 2026.
Source: Mathews-Tom/armory on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.