Borrowing it
Nothing to install: this file belongs to gaoconggit/SharpPad. 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/gaoconggit/SharpPad/main/.claude/commands/review-code.mdgit clone --depth 1 https://github.com/gaoconggit/SharpPadWrote 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/gaoconggit/sharppad/review-code)<a href="https://agentmods.dev/commands/gaoconggit/sharppad/review-code"><img src="https://agentmods.dev/badge/commands/gaoconggit/sharppad/review-code/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/gaoconggit/sharppad/review-code"><img src="https://agentmods.dev/badge/commands/gaoconggit/sharppad/review-code.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.01002 |
| Opus 5.5 | $0.00000 | $0.00401 |
| Sonnet 5.5 | $0.00000 | $0.00200 |
| Haiku 4.5 | $0.00000 | $0.00100 |
Grade A, and why
review-code 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.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/review-code - Code Review Command
Launches the professional code review agent for comprehensive quality, security, and maintainability analysis.
Syntax
/review-code [file_path | code_snippet | pattern]
Description
Activates the code-reviewer agent to perform thorough code analysis covering:
- Logic correctness and edge cases
- Security vulnerabilities and best practices
- Performance optimization opportunities
- Code maintainability and standards compliance
- Framework-specific recommendations
Examples
Basic Usage
Review current file
/review-code
Review specific file
/review-code src/utils/helper.js
Review code snippet
/review-code
function validateUser(user) {
if (user.name && user.email) {
return true;
}
return false;
}
Review multiple files
/review-code src/components/*.tsx
Advanced Usage
Focus on security issues
/review-code --focus=security UserController.cs
Performance optimization review
/review-code --focus=performance src/data/queries.js
Review recent changes
/review-code --changes
Parameters
Focus Areas
--focus=security- Prioritize security vulnerability analysis--focus=performance- Emphasize performance optimization--focus=maintainability- Focus on code structure and readability--focus=standards- Check coding standards and conventions
Scope Options
--changes- Review only recent Git changes--modified- Review modified files in working directory--staged- Review staged files for commit
Review Depth
--quick- Fast review focusing on critical issues only--thorough- Comprehensive analysis including style suggestions--strict- Strictest review mode with all checks enabled
Review Categories
The command produces structured output with issues categorized by severity:
🔴 Critical Issues (Must Fix)
- Logic errors and potential runtime failures
- Security vulnerabilities (SQL injection, XSS, authentication bypasses)
- Performance problems (memory leaks, blocking operations)
- Breaking changes or API compatibility issues
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 · 170 lines · 0 tokens per session scan A 5951fb7e8f7d
review-code is a command published in the GitHub repository gaoconggit/SharpPad (83 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,002 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
step5-review-gate
Pipeline Step 5 — Independent review gate and drift detection. Run in a fresh agent session (read-only audit).
step4-completeness-sweep
Pipeline Step 4 — Completeness sweep to eliminate TODOs, mocks, stubs, and placeholder code before review.
code-review
../../.cratis/ai/prompts/code-review.prompt.md.
local-code-review-tests
Review uncommitted changes, build projects, and run unit tests.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.