Review Queue Claude Code mod: a Claude Code review queue for changed files
Group changed files by purpose, mark each reviewed, and see it go STALE when the staged or unstaged diff changes.
Permissions
- Reads filesCan read files and list directories on your machine ($.fs.read / list / stat / exists).
- Runs commandsCan run shell programs on your machine ($.process.run / spawn). Check the source for exactly which ones.
- Intercepts tool callsSees every tool call Claude makes (tool.call / tool.check) and could block or change it.
- Changes the UIDraws into the Claude Code interface: bands, panes, status text, toasts (ui.render / $.ui.*).
- Adds commands/toolsRegisters new slash commands or tools that you or Claude can invoke ($.command.register / $.tool.register).
- Stores dataKeeps data between sessions in the plugin's private store ($.store.*).
- tested with
- v2.1.310
- last tested
- requires
- Claude Code ≥ 2.1.287
- surfaces
- transcript
- source
- YeonwooSung (Apache-2.0)
Install inside Claude Code:
/plugin install review-queue --marketplace YeonwooSung/my-claude-code-modsWhat does this mod do?
Review Queue is a community mod by YeonwooSung (YeonwooSung), one plugin in the author's my-claude-code-mods collection. It gives Claude Code a review queue: a checklist of the files you have changed, sorted by purpose, where each file is PENDING, REVIEWED, STALE or UNKNOWN. It is for the moment after Claude has edited a dozen files and you want to be sure you have actually read each one.
Everything runs through one slash command, /review-queue. According to its help text and the author's README:
/review-queue group <purpose> | <path>puts a changed file under a purpose heading such as "Authentication". Files without a group appear under "Ungrouped"./review-queue mark <path>records that you reviewed the file as it is now. Only files git reports as changed can be marked./review-queue unmark <path>removes the mark./review-queue list(or just/review-queue) prints the queue./review-queue resetclears the saved groups and marks.
A file is REVIEWED only while its staged diff, unstaged diff and working-file bytes still match what they were when you marked it. If any of them changes, it shows as STALE. If the mod cannot get complete evidence, for example for a symlink, a file over 2 MiB or a git error, it shows UNKNOWN or an INCOMPLETE line instead of claiming the file is reviewed.
Install
The install block above adds the author's marketplace and installs the plugin from it. Then run /reload-plugins or restart Claude Code. Run /review-queue from the root of the repository you are working in.
$ install review-queue
Requires Claude Code ≥ 2.1.287
Installs from the author's own marketplace: YeonwooSung/my-claude-code-mods
1.One line, inside Claude Code
/plugin install review-queue --marketplace YeonwooSung/my-claude-code-modsPaste into a running session (v2.1.275+). Claude Code asks to add the marketplace first.
2.From your shell
claude plugin marketplace add YeonwooSung/my-claude-code-mods claude plugin install review-queue@my-claude-code-modsThen run /reload-plugins in any session that is already open.
3.Try it without installing
git clone https://github.com/YeonwooSung/my-claude-code-mods claude --plugin-dir ./my-claude-code-mods/review-queueLoads the mod for one session only. Nothing is added to your settings.
How it works
The plugin is a function-hooks module, hooks/register.ts, plus the review logic in hooks/core/feature.ts. On session.start it registers the command. A command.run hook answers only /review-queue. For each changed path it builds a signature from two git diffs and the file's bytes:
const staged = await git(io, ['diff', '--no-ext-diff', '--no-textconv', '--binary', '--cached', 'HEAD', '--', path])
const unstaged = await git(io, ['diff', '--no-ext-diff', '--no-textconv', '--binary', '--', path])
...
return hash(JSON.stringify([staged, unstaged, body]))That hash is compared with the one saved when you ran mark. The adapter only lets process.run start git, with a 10 second timeout. State is kept per working directory and session ID in the plugin store, so resuming the same session restores your groups and marks. The tool.call hook is present but does nothing here: it checks whether the feature class has an observe method, which this one does not, and then forwards the call unchanged.
Customize it
There are no /config options. The only inputs are the command's arguments: a purpose is free text up to 500 characters, and the path must be inside the project and may not contain ... Several files can share a purpose by running group once per file. Running group again for the same path replaces its purpose. Lists are capped at 200 entries.
Permissions & safety
We read every file the plugin can load: the manifest, hooks/hooks.json, register.ts, core/feature.ts, core/redact.ts, core/runtime.ts and the two test files. There is no package.json inside the plugin, no binary and no minified code. Here is what we found:
- Network: none in the code. We searched for
fetch, URLs, sockets andchild_processand found no matches. - Processes:
gitonly, enforced inregister.ts(any otherargv[0]throws). The calls aregit -C <cwd> status --porcelain=v1 -z --untracked-files=allandgit -C <cwd> diff --no-ext-diff --no-textconv --binary [--cached] HEAD -- <path>. Arguments are passed as an array, with no shell. - File reads and writes: it reads changed files in the project to fingerprint them. It writes nothing to your project,
~/.claude, shell files or settings. Its records (purpose text, paths, hashes) go to the plugin store through$.store, limited to 256 KiB. - Daemons, telemetry, secrets: no background process, no telemetry, and no environment variable or credential is read. Text it stores or prints has terminal escapes stripped and obvious secrets masked by a best-effort redactor, which the author says may miss some.
- Prompt influence and gating: it injects nothing into prompts.
validatelistscommand.runandtool.callas gating hooks without.catch, but thetool.callhook returns the original result unchanged, and the command hook answers only/review-queue. - Obfuscation: none. The README has a long section arguing that its regexes and constructors are harmless; we checked those claims against the code and they hold.
- License: Apache-2.0, from the
LICENSEfile at the repository root.
One general git caveat: git itself reads the repository's configuration, so run this in repositories you trust. claude plugin validate passed with no errors or warnings. claude plugin test ran 7 tests in 2 files, and all passed. The README says live terminal and Desktop rendering was not checked by the author.
- Reads files
- Can read files and list directories on your machine ($.fs.read / list / stat / exists).
- Runs commands
- Can run shell programs on your machine ($.process.run / spawn). Check the source for exactly which ones.
- Intercepts tool calls
- Sees every tool call Claude makes (tool.call / tool.check) and could block or change it.
- Changes the UI
- Draws into the Claude Code interface: bands, panes, status text, toasts (ui.render / $.ui.*).
- Adds commands/tools
- Registers new slash commands or tools that you or Claude can invoke ($.command.register / $.tool.register).
- Stores data
- Keeps data between sessions in the plugin's private store ($.store.*).
Compatibility & troubleshooting
We loaded it on Claude Code 2.1.310, and the author reports testing on 2.1.302. It needs function hooks and git on your PATH. If something looks wrong:
INCOMPLETE: changed files unavailablemeansgit statusfailed. Run the command from the root of a git repository.File not changed; review not markedmeans git does not list that path as changed. Check the path is relative to the project.Session changed; operation not appliedmeans the working directory or session changed while the command ran. Run it again.- Ignored files are never listed, because the mod relies on git's own view of changes.
To check that it works, edit a tracked file, run /review-queue mark <path>, then edit the file again and run /review-queue list. The file should move from REVIEWED to STALE.
FAQ
- What does STALE mean in the Claude Code review queue?
- You marked the file as reviewed, and its fingerprint has changed since. The fingerprint covers the staged diff, the unstaged diff and the working-file bytes, so editing the file, or staging a different change, moves it from REVIEWED to STALE. Mark it again after you have looked at the new version.
- Does Review Queue read my whole repository?
- No. It asks git for the list of changed files (git status) and, for each of up to 200 of them, reads that file's diffs and the file itself, up to 2 MiB. Unchanged files are not read, and symlinks are skipped and reported as UNKNOWN.
- Does Review Queue send anything over the network or edit my code?
- Not in the code we read. There are no HTTP calls, and the only process it starts is git with fixed read-only arguments. It never edits project files; its records go to the plugin's own store, keyed by working directory and session.
- Can Claude mark files as reviewed for me?
- Not through this mod. It registers no tool and adds nothing to prompts. Marking happens only when you type /review-queue mark with a path, so a REVIEWED line reflects a decision you made.
- How do I clear the queue?
- Run /review-queue reset to clear the saved groups and review marks for the current folder and session. Run /review-queue unmark followed by a path to clear a single file.
# Related mods
FeaturedTime Machine
A branching timeline of every tool call, with shadow-git snapshots you can diff, restore, branch and rerun.
- status
- pane
- Reads files
- Writes files
- Runs commands
- Intercepts tool calls
- Reads your prompts
- Changes the UI
- Adds commands/tools
- Stores data
tested with v2.1.303
FeaturedGit Branch Above Prompt
Shows your git branch, changed-file count and ahead/behind status in a one-line band above the Claude Code prompt.
- above-prompt
- Runs commands
- Intercepts tool calls
- Changes the UI
tested with v2.1.310
More in Git & GitHub, Timers, todos, standups.