Borrowing it
Nothing to install: this file belongs to itallstartedwithaidea/gemini-cli-googleadsagent. 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/itallstartedwithaidea/gemini-cli-googleadsagent/main/.gemini/commands/oncall/pr-review.tomlgit clone --depth 1 https://github.com/itallstartedwithaidea/gemini-cli-googleadsagentWrote 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/commands/itallstartedwithaidea/gemini-cli-googleadsagent/pr-review)<a href="https://agentmods.dev/commands/itallstartedwithaidea/gemini-cli-googleadsagent/pr-review"><img src="https://agentmods.dev/badge/commands/itallstartedwithaidea/gemini-cli-googleadsagent/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/commands/itallstartedwithaidea/gemini-cli-googleadsagent/pr-review"><img src="https://agentmods.dev/badge/commands/itallstartedwithaidea/gemini-cli-googleadsagent/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.00000 | $0.00736 |
| Opus 5.5 | $0.00000 | $0.00294 |
| Sonnet 5.5 | $0.00000 | $0.00147 |
| Haiku 4.5 | $0.00000 | $0.00074 |
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 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 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description = "Review a specific pull request"
prompt = """
Mission: Comprehensive Pull Request Review
Today, our mission is to meticulously review community pull requests (PRs) for this project. We will proceed systematically, evaluating each candidate PR for its quality, adherence to standards, and readiness for merging.
Workflow:
-
PR Preparation & Initial Assessment:
- You will check out the designated PR {{args}} into a temporary branch.
- Execute the preflight checks (
npm run preflight). This includes building, linting, and running all unit tests. - Analyze the output of these preflight checks, noting any failures, warnings, or linting issues.
-
In-Depth Code Review:
- Your primary role is to conduct a thorough and in-depth code review of the changes introduced in the PR. Focus your analysis on the following criteria:
- Correctness: Does the code achieve its stated purpose without bugs or logical errors?
- Maintainability: Is the code clean, well-structured, and easy to understand and modify in the future? Consider factors like code clarity, modularity, and adherence to established design patterns.
- Readability: Is the code well-commented (where necessary) and consistently formatted according to our project's coding style guidelines?
- Efficiency: Are there any obvious performance bottlenecks or resource inefficiencies introduced by the changes?
- Security: Are there any potential security vulnerabilities or insecure coding practices?
- Edge Cases and Error Handling: Does the code appropriately handle edge cases and potential errors?
- Testability: Is the new or modified code adequately covered by tests (even if preflight checks pass)? Suggest additional test cases that would improve coverage or robustness.
- Based on your analysis, you will determine if the PR is safe to merge.
- Your primary role is to conduct a thorough and in-depth code review of the changes introduced in the PR. Focus your analysis on the following criteria:
-
Reviewing Previous Feedback:
- Access and examine the PR's history to identify any outstanding requests or unresolved comments from previous reviews. Incorporate these into your current review and explicitly highlight if they have been adequately addressed in the current state of the PR.
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 · 48 lines · 0 tokens per session scan A c90e5d521621
pr-review is a command published in the GitHub repository itallstartedwithaidea/gemini-cli-googleadsagent (6 stars, last pushed 11d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 736 tokens. A static security scan graded it A with 0 findings. It is 100% identical to pr-review, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
pr-ready
Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.
dart-review-pr
review a PR or address review feedback.
add-test
Adds a unit test for one function.
test
A command that runs JavaScript or TypeScript tests with npm or Vitest, a test-runner tool, and explains any failures.
refactor-sprint
Parallel refactor sprint — fires refactor-cleaner + code-simplifier + type-design-analyzer + tdd-guide simultaneously. Full cleanup in one pass.
quality-check-command
This command performs comprehensive code quality checks. Use it before commits or when implementation is complete.