Borrowing it
Nothing to install: this file belongs to justomsharma/github-resume-assistant. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/justomsharma/github-resume-assistant/main/.claude/skills/review-pr/SKILL.mdgit clone --depth 1 https://github.com/justomsharma/github-resume-assistantWrote 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/justomsharma/github-resume-assistant/review-pr)<a href="https://agentmods.dev/skills/justomsharma/github-resume-assistant/review-pr"><img src="https://agentmods.dev/badge/skills/justomsharma/github-resume-assistant/review-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.
<a href="https://agentmods.dev/skills/justomsharma/github-resume-assistant/review-pr"><img src="https://agentmods.dev/badge/skills/justomsharma/github-resume-assistant/review-pr.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.00051 | $0.00440 |
| Opus 5.5 | $0.00020 | $0.00176 |
| Sonnet 5.5 | $0.00010 | $0.00088 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
review-pr 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 2mo 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.
What it actually says
review-pr
Review a PR before it merges. Follow docs/GIT_WORKFLOW.md. Review as a skeptic,
even on your own PR — it catches bugs and builds the exact habit that impresses
senior engineers.
Get the diff
gh pr view <number>
gh pr diff <number>
Review dimensions (in order)
- Correctness — Does it do what the PR says? Trace edge cases, especially the empty-GitHub path. Any bug, missed branch, or wrong assumption?
- Scope — Stays within one ROADMAP item? Any creep or unrelated changes?
- Practices (CODING_PRACTICES.md) — Types, error handling, no secrets,
core/free of MCP imports, no dead code? - Tests (TESTING.md) — Adequate coverage? External calls mocked? Empty-GitHub case tested where relevant?
- Clarity — Could someone else maintain this in six months?
Leave findings
- Specific and actionable:
file:line+ the problem + a suggested fix. - Be direct and kind. Distinguish must-fix (correctness, secrets, tests) from nits.
Decision
- Request changes if correctness, secrets, or tests fail → send the author back
to
/plan-firstor/implementas appropriate. - Approve only when correctness holds and tests pass.
Merge
- Squash-merge to keep
mainhistory clean (GIT_WORKFLOW.md). - Confirm the ROADMAP.md checkbox is ticked if the item is complete.
Handoff
This is the end of the chain. After merge, the next unit of work starts fresh at
/plan-first.
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.
- 2mo ago First seen · 50 lines · 51 tokens per session scan A 95d3e7485033
review-pr is a skill published in the GitHub repository justomsharma/github-resume-assistant (0 stars, last pushed 3mo ago), licensed MIT. It adds 51 tokens to every session and 440 once invoked, about $0.0002 per session on Opus 5.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
babysit
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.
code-review
Review the current diff, or a PR number/branch/path target, for correctness bugs (plus reuse/simplification/efficiency cleanups where the model's recipe covers them) at the effort level given first, before any target (low|medium|high|xhigh|max: from few high-confidence findings to many, some uncertain; ultra: deep…
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
babysit
Watch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in /babysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.
make-pr-easy-to-review
Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for "make this easy to review", "tidy this PR", "clean up commits", or "annotate the diff".