sumulige-claude: Command for Claude Code

.claude/commands/review.md

review is a command for Claude Code from sumulige/sumulige-claude. It costs 5 tokens per session (312 once invoked), scanned A, original, MIT.

A command for inspecting and evaluating current uncommitted or staged code changes before they are committed.

In plain words
What is it for?
Use it to review diffs and check functionality, security, code quality, testing, performance, and error handling.
Why use it?
It helps catch bugs, security problems, missing tests, edge-case failures, and unnecessary complexity before changes are recorded.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is sumulige/sumulige-claude's own configuration. It tells Claude Code how to work on sumulige-claude itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything sumulige-claude configures →

Reuse

Borrowing it

Nothing to install: this file belongs to sumulige/sumulige-claude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/sumulige/sumulige-claude/main/.claude/commands/review.md
Clone the repo
git clone --depth 1 https://github.com/sumulige/sumulige-claude

Made for: Claude Code.

Wrote 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.

agentmods badge for review

README.md
[![agentmods](https://agentmods.dev/badge/commands/sumulige/sumulige-claude/review.svg)](https://agentmods.dev/commands/sumulige/sumulige-claude/review)
Your own site
<a href="https://agentmods.dev/commands/sumulige/sumulige-claude/review"><img src="https://agentmods.dev/badge/commands/sumulige/sumulige-claude/review.svg" alt="Measured on agentmods" height="20"></a>
Per session 5 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 312 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00005 $0.00312
Opus 5 $0.00003 $0.00156
Sonnet 5 $0.00001 $0.00062
Haiku 4.5 $0.00001 $0.00031

Measured 6d ago against content hash 88f7ca41900c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

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 6d 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.

.claude/commands/review.md · 62 lines

What it actually says

Review the current uncommitted or staged changes.

Step 1: Show Changes

git status

# Show unstaged changes
git diff

# Show staged changes
git diff --staged

Step 2: Code Review Checklist

Review the changes for:

Functionality

  • Does the change accomplish the intended goal?
  • Are there any obvious bugs or logic errors?
  • Are edge cases handled?

Security

  • No hardcoded credentials or API keys
  • No SQL injection, XSS, or other vulnerabilities
  • Proper input validation

Code Quality

  • Code is readable and self-documenting
  • No unnecessary complexity
  • Follows DRY (Don't Repeat Yourself)
  • Proper error handling

Testing

  • Tests cover new functionality
  • No tests are broken
  • Edge cases are tested

Performance

  • No obvious performance issues
  • No unnecessary database queries or API calls
  • Proper use of caching (if applicable)

Step 3: Provide Feedback

For each issue found:

  1. Point out the specific file and line
  2. Explain the issue
  3. Suggest a fix

Step 4: Summary

Provide an overall assessment:

  • ✅ Ready to commit
  • ⚠️ Minor issues to address
  • ❌ Major issues that need fixing
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.

  1. 6d ago First seen · 62 lines · 5 tokens per session scan A 88f7ca41900c

Subscribe to this mod's changes

review is a command published in the GitHub repository sumulige/sumulige-claude (2 stars, last pushed 6mo ago), licensed MIT. It adds 5 tokens to every session and 312 once invoked, about $0.0000 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.