Borrowing it
Nothing to install: this file belongs to vishnu2kmohan/mcp-server-langgraph. 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/vishnu2kmohan/mcp-server-langgraph/main/.claude/commands/review-pr.mdgit clone --depth 1 https://github.com/vishnu2kmohan/mcp-server-langgraphWrote 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/vishnu2kmohan/mcp-server-langgraph/review-pr)<a href="https://agentmods.dev/commands/vishnu2kmohan/mcp-server-langgraph/review-pr"><img src="https://agentmods.dev/badge/commands/vishnu2kmohan/mcp-server-langgraph/review-pr.svg" alt="Measured on agentmods" 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.00016 | $0.01803 |
| Opus 5 | $0.00008 | $0.00901 |
| Sonnet 5 | $0.00003 | $0.00361 |
| Haiku 4.5 | $0.00002 | $0.00180 |
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 7d 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 — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Pull Request
Comprehensive PR review checklist to ensure code quality, testing, and best practices.
Usage
/review-pr
Pre-Review Setup
1. Fetch PR Code
# Using gh CLI
gh pr checkout <PR_NUMBER>
# Or manual checkout
git fetch origin pull/<PR_NUMBER>/head:pr-<PR_NUMBER>
git checkout pr-<PR_NUMBER>
2. Understand Changes
# View files changed
git diff main...HEAD --stat
# View detailed diff
git diff main...HEAD
# View commits in PR
git log main..HEAD --oneline
Review Checklist
Code Quality
Readability
- Code is self-explanatory (minimal comments needed)
- Variable/function names are descriptive
- Functions are small and focused (< 50 lines ideally)
- No deeply nested conditionals (< 4 levels)
- Consistent with existing code style
Design
- Follows SOLID principles
- No code duplication (DRY)
- Proper separation of concerns
- Uses appropriate design patterns
- Follows existing architectural patterns (check ADRs)
Type Safety
- All functions have type hints
- Type hints are accurate and helpful
- No unnecessary
Anytypes - Proper handling of Optional types
- MyPy passes (or errors documented)
Testing
Test Coverage
- New code has tests (TDD followed)
- Tests cover happy path
- Tests cover edge cases
- Tests cover error scenarios
- Coverage ≥ 80% for new code
Test Quality
- Tests are independent (no shared state)
- Tests are deterministic (not flaky)
- Test names are descriptive (test_X_when_Y_then_Z format)
- Proper use of fixtures
- No test code duplication
Test Execution
# Run all tests
make test-all-quality
# Run with coverage
pytest --cov=src --cov-report=term-missing tests/
# Check for flaky tests
pytest tests/ --count=5
Security
- No hardcoded credentials or secrets
- Input validation implemented
- SQL injection prevention (parameterized queries)
- XSS prevention (proper output encoding)
- Command injection prevention
- Path traversal prevention
- Authentication checks on protected endpoints
- Authorization checks (OpenFGA)
- Rate limiting considered (if public endpoint)
- Secrets in environment variables or Infisical
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.
- 7d ago First seen · 328 lines · 16 tokens per session scan A 5a951e6c4103
review-pr is a command published in the GitHub repository vishnu2kmohan/mcp-server-langgraph (4 stars, last pushed 7d ago), licensed MIT. It adds 16 tokens to every session and 1,803 once invoked, about $0.0001 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-31.
Other commands, from other repositories
pr-manager
Comprehensive pull request management with ruv-swarm coordination for automated reviews, testing, and merge workflows.
triage
Triages a PR comment — from a bot (Copilot, CI) or a human reviewer. Fetches the comment and diff via gh CLI, classifies it, applies the fix directly to the file if valid, posts a reply on the thread, and resolves it. Run from inside the repo.
pr
Analyze changes, detect scope issues, and create a well-structured PR.
review-pr
A command for reviewing a GitHub pull request, which is a proposed code change waiting to be merged. It examines the changes and can leave review comments or approve the pull request when the findings pass.
review-branch
Review an existing branch holistically before merging — blast radius, conventions, security, and spec compliance.
align
Context-aware alignment. When in plan mode, it reviews the active plan. Otherwise, it reviews all branch changes against Ion quality gates and principles, implements the fixes and commits them after operator approval.