Borrowing it
Nothing to install: this file belongs to ashaychangwani/imprint. 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/ashaychangwani/imprint/main/.agents/skills/pr-review-convergence/SKILL.mdgit clone --depth 1 https://github.com/ashaychangwani/imprintWrote 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/ashaychangwani/imprint/pr-review-convergence)<a href="https://agentmods.dev/skills/ashaychangwani/imprint/pr-review-convergence"><img src="https://agentmods.dev/badge/skills/ashaychangwani/imprint/pr-review-convergence/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/ashaychangwani/imprint/pr-review-convergence"><img src="https://agentmods.dev/badge/skills/ashaychangwani/imprint/pr-review-convergence.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00082 | $0.01122 |
| Opus 5 | $0.00041 | $0.00561 |
| Sonnet 5 | $0.00016 | $0.00224 |
| Haiku 4.5 | $0.00008 | $0.00112 |
Grade A, and why
pr-review-convergence 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 11d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Review Convergence
Drive the branch to a genuinely reviewable state. Treat “open the PR” as an intermediate step; completion requires green checks and no unresolved actionable review findings.
1. Establish scope and guardrails
- Read repository instructions such as
AGENTS.md,CLAUDE.md, contributing guidance, and relevant local skills completely. - Inspect
git status, the current branch, remotes, upstream, source branch, complete diff, and recent history. Preserve unrelated user changes. - Never use destructive resets or force-push without explicit authorization. Never bypass hooks. Stop if the diff contains credentials, recordings, personal data, or another public-repository violation.
- Match mutations to the user's authority. A review-only request permits inspection and local validation, not commits, pushes, or PR creation. Only proceed through remote steps when the user explicitly asked to prepare, create, push, or update the PR/MR; otherwise stop after the review handoff.
- Create a short plan covering rebase, validation, review rounds, commit, push, PR creation, and check monitoring.
2. Rebase safely before review
Skip this section for review-only requests: inspect the branch against its declared source without stashing, rebasing, committing, or otherwise mutating the user's worktree.
Fetch the source branch, normally origin/main. If the worktree is dirty,
stash tracked and untracked changes under a descriptive name, rebase, restore
the stash, and verify every change returned. Resolve straightforward conflicts
without discarding either side; ask only when resolution changes product
intent.
Record the rebased commit so later source-branch movement can be detected.
3. Validate the implementation
Run repository-prescribed checks before asking reviewers to inspect avoidable failures. At minimum for Imprint:
bun run lint
bun run typecheck
bun test
git diff --check
Run focused tests for changed behavior. If the website changed, build it and visually inspect desktop and mobile layouts. Exercise important behavior live when safe and proportionate. Distinguish an unrelated flaky test from a real failure by reproducing it in isolation, then rerun the full gate; do not simply dismiss it.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 123 lines · 82 tokens per session scan A ad9d27d1771e
pr-review-convergence is a skill published in the GitHub repository ashaychangwani/imprint (21 stars, last pushed 3d ago), licensed MIT. It adds 82 tokens to every session and 1,122 once invoked, about $0.0004 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.
Other skills, from other repositories
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
github
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available)…
issue-to-pr-resolver
Implement a GitHub issue end-to-end — create a worktree branch, implement the feature with tests, create a draft PR, then iteratively resolve all CI failures and review comments until the PR is clean. Use when you need to fully implement a GitHub issue from start to merge-ready. Triggers on "implement issue", "resolve…
my-pr-checker
Manage your own GitHub pull requests — check CI status, inline review comments, PR-level comments, resolve review threads, fix issues, and iterate until all checks pass and threads are resolved. Use for managing your own PRs (not external contributions). Triggers on "check my PR", "check PR", "/my-pr-checker ".
meta-codereview-current-diff
Read the current uncommitted diff, run three independent reviewers (safety + tests-coverage + style) in parallel, then arbitrate a single BLOCK / BLOCKWITHOVERRIDE / PASSWITHNOTES verdict. Use before commit when you want a multi-perspective second-opinion instead of a single-reviewer agent loop.
goal-pr
Drive a pull request to a clean state and merge it: run the review-pr skill, fix every mid-or-above finding, and repeat until no mid-or-above findings remain, then merge. Use when the user wants to finish a PR by reviewing, fixing, and merging it, or triggers on "the goal-pr skill".