What is review-changes?

A read-only command that reviews recently changed source code for duplication, unnecessary complexity, project inconsistencies, and rule violations, then records its findings.

Use it after changes to inspect a Git diff, receive a findings table, and save the review for a later cleanup command.

It gives developers a prioritized list of improvements without modifying the source or committing anything.

review-changes — Command for Claude Code by sefaertunc: A read-only command that reviews recently changed source code…

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/sefaertunc/worclaude/review-changes

Clone the repo

git clone --depth 1 https://github.com/sefaertunc/Worclaude

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/sefaertunc/worclaude/review-changes.svg)](https://agentmods.dev/commands/sefaertunc/worclaude/review-changes)

Your own site

<a href="https://agentmods.dev/commands/sefaertunc/worclaude/review-changes"><img src="https://agentmods.dev/badge/commands/sefaertunc/worclaude/review-changes.svg" alt="Measured on agentmods" height="20"></a>

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 455 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.

Model	Per session	Once invoked
Fable 5	$0.00013	$0.00455
Opus 5	$0.00006	$0.00228
Sonnet 5	$0.00003	$0.00091
Haiku 4.5	$0.00001	$0.00046

Measured 4d ago against content hash 10b965f43b7e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

review-changes 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 4d 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-changes.md · 59 lines

What it actually says

Review changed code for reuse, quality, and efficiency.

CRITICAL: This is a READ-ONLY review of source files. You MUST NOT edit source files. You MUST NOT make any commits. You MUST NOT stage changes. Only analyze, report, and write one scratch artifact (see step 4).

Process

Read recent changes (git diff HEAD~1 or staged changes).
Check for:
- Duplicated code or missed reuse opportunities
- Unnecessary complexity or abstraction
- Inconsistency with project patterns
- CLAUDE.md compliance issues

Report findings as a prioritized table to the user:

| Finding | Category | Action |
|---------|----------|--------|
| [what]  | [type]   | Fix / Skip — [reason] |

Write the findings to .claude/scratch/last-review.md with SHA frontmatter so /refactor-clean can pick them up without re-analyzing.
```
---
created: <YYYY-MM-DDTHH:MM:SSZ>
sha: <git rev-parse HEAD>
command: /review-changes
---

# Findings

| Finding | Category | Action |
|---------|----------|--------|
| ...     | ...      | ...    |
```
Capture the SHA via git rev-parse HEAD at the moment of writing. If .claude/scratch/last-review.md already exists, overwrite it — only the most recent review is consumed.

Writing this file is the ONLY filesystem mutation /review-changes performs. Source files remain untouched.

The user will decide which findings to act on. They can run /refactor-clean next; it will read the scratch file and use the findings as a work plan (skipping its own analysis when the SHA matches).

Trigger Phrases

"review my changes"
"what did I change"
"code review"

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.

4d ago First seen · 59 lines · 13 tokens per session scan A 10b965f43b7e

Subscribe to this mod's changes

review-changes is a command published in the GitHub repository sefaertunc/Worclaude (4 stars, last pushed 25d ago), licensed MIT. It adds 13 tokens to every session and 455 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.

Code review ai ai-agent ai-agents ai-tools automation claude

review-changes

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Process

Trigger Phrases

What this file has done since we first saw it

Other commands, from other repositories

statusbar-style

fest-show

superpowers-execute

config

deps-age

session-active