Borrowing it
Nothing to install: this file belongs to slayer/gcon. 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/slayer/gcon/master/.claude/commands/read-review.mdgit clone --depth 1 https://github.com/slayer/gconWrote 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/slayer/gcon/read-review)<a href="https://agentmods.dev/commands/slayer/gcon/read-review"><img src="https://agentmods.dev/badge/commands/slayer/gcon/read-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/slayer/gcon/read-review"><img src="https://agentmods.dev/badge/commands/slayer/gcon/read-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.00255 |
| Opus 5.5 | $0.00000 | $0.00102 |
| Sonnet 5.5 | $0.00000 | $0.00051 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
read-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 13d 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
Read and Address PR Review Comments
Fetch review comments from the current branch's PR and address any issues.
Steps
- Get the current branch name
- Find the PR associated with this branch
- Fetch all review comments using:
gh api repos/{owner}/{repo}/pulls/{pr_number}/comments - Parse and display each comment with:
- File path and line number
- Comment body
- Any code suggestions
- For each comment:
- Analyze if it's actionable (bug fix, code improvement, etc.)
- If applicable, implement the fix
- Run tests to verify the fix doesn't break anything
- After addressing all comments:
- Commit the fixes with a descriptive message
- Push to update the PR
- Resolve the comments in the PR if possible
Output Format
For each comment, show:
---
File: {path}:{line}
Issue: {brief description}
Status: {Fixed | Skipped | N/A}
---
Notes
- Skip comments that are just questions or acknowledgments
- Group related comments when possible
- Always run
go build ./...andgo test ./...after making changes
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.
- 13d ago First seen · 39 lines · 0 tokens per session scan A 406c2c6a4821
read-review is a command published in the GitHub repository slayer/gcon (8 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 255 tokens. 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-10-02.
Other commands, from other repositories
elegant-code-review
Review the current working diff against the elegant-code decision ladder and propose deletions, honoring the negligence floor.
prp-commit
Quick commit with natural language file targeting: describe what to commit in plain English.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
gsd:pr-branch
Create a clean PR branch by filtering out .planning/ commits — ready for code review.
karpathy-check
Revisa as alterações em stage (ou o último commit) com base nos 4 princípios de codificação do Karpathy. Verifica complexidade, ruído no diff, suposições ocultas e verificação de objetivos. Uso: /karpathy-check [--last-commit].
validate-pr-description
Use when validating a PR title and description for conventional commit format, issue linking keywords, and template compliance before submission.