Borrowing it
Nothing to install: this file belongs to priyanshuchawda/tracepilot-gemini-cli. 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/priyanshuchawda/tracepilot-gemini-cli/main/.gemini/skills/async-pr-review/SKILL.mdgit clone --depth 1 https://github.com/priyanshuchawda/tracepilot-gemini-cliWrote 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/priyanshuchawda/tracepilot-gemini-cli/async-pr-review)<a href="https://agentmods.dev/skills/priyanshuchawda/tracepilot-gemini-cli/async-pr-review"><img src="https://agentmods.dev/badge/skills/priyanshuchawda/tracepilot-gemini-cli/async-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/priyanshuchawda/tracepilot-gemini-cli/async-pr-review"><img src="https://agentmods.dev/badge/skills/priyanshuchawda/tracepilot-gemini-cli/async-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.00037 | $0.00792 |
| Opus 5 | $0.00018 | $0.00396 |
| Sonnet 5 | $0.00007 | $0.00158 |
| Haiku 4.5 | $0.00004 | $0.00079 |
Grade A, and why
async-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 10d 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.
This is a copy
100% identical to async-pr-review — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Async PR Review
This skill provides a set of tools to asynchronously review a Pull Request. It will create a background job to run the project's preflight checks, execute Gemini-powered test plans, and perform a comprehensive code review using custom prompts.
This skill is designed to showcase an advanced "Agentic Asynchronous Pattern":
- Native Background Shells vs Headless Inference: While Gemini CLI can natively spawn and detach background shell commands (using the
run_shell_commandtool withis_background: true), a standard bash background job cannot perform LLM inference. To conduct AI-driven code reviews and test generation in the background, the shell script must invoke thegeminiexecutable headlessly using-p. This offloads the AI tasks to independent worker agents. - Dynamic Git Scoping: The review scripts avoid hardcoded paths. They use
git rev-parse --show-toplevelto automatically resolve the root of the user's current project. - Ephemeral Worktrees: Instead of checking out branches in the user's main workspace, the skill provisions temporary git worktrees in
.gemini/tmp/async-reviews/pr-<number>. This prevents git lock conflicts and namespace pollution. - Agentic Evaluation (
check-async-review.sh): The check script outputs clean JSON/text statuses for the main agent to parse. The interactive agent itself synthesizes the final assessment dynamically from the generated log files.
Workflow
- Determine Action: Establish whether the user wants to start a new async review or check the status of an existing one.
- If the user says "start an async review for PR #123" or similar, proceed to Start Review.
- If the user says "check the status of my async review for PR #123" or similar, proceed to Check Status.
Start Review
If the user wants to start a new async PR review:
- Ask the user for the PR number if they haven't provided it.
- Execute the
async-review.shscript, passing the PR number as the first argument. Be sure to run it with theis_backgroundflag set to true to ensure it immediately detaches..gemini/skills/async-pr-review/scripts/async-review.sh <PR_NUMBER> - Inform the user that the tasks have started successfully and they can check the status later.
What ships with it
3 files 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.
- 10d ago First seen · 45 lines · 37 tokens per session scan A 1502652fdef0
async-pr-review is a skill published in the GitHub repository priyanshuchawda/tracepilot-gemini-cli (1 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 792 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to async-pr-review, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
code-review-and-quality
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
code-graph-review
Use BEFORE a commit or change review, when you need to understand "what this N-file change will break": blast radius over the diff, affected execution paths, dead code, architectural hubs/bridges, weak spots, rename with preview. Do not use for code search — CRG is for structural diff analysis, not navigation.
fable-judge
Adversarial verification of finished work: re-runs the claimed verifications, diffs what changed, detects false "done" claims, delivers an evidence-based verdict (VERIFIED / VERIFIED WITH CAVEATS / REFUTED). Use after any agent or model claims work is complete — "/fable-judge", "judge this work", "verify what it did".…
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements.
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.
spec-kitty-mission-review
Review a fully merged Spec Kitty mission post-merge (all WPs done/approved) to verify spec→code fidelity, FR coverage, drift, risks, and security. Triggers: "review the merged mission", "post-merge mission review", "verify the completed mission", "audit the mission implementation", "mission-level acceptance review"…