review · indxdev — Claude Code command: what it does, how to install
review — a Claude Code command checks what got worse in a pull request or recent commits. Run it with a PR number or revision.
MIT ★ 113 updated 2026-11-15
/plugin marketplace add INDXDev/jevlint
/plugin install jevlint@jevlintWhat review does
The review command compares changes and reports regressions by file and line, naming the pull request or commit. It uses AST metrics: a numeric argument runs jevlint pr <number> --ast-only; other arguments run jevlint commits <revision> --count 5 --ast-only.
The PR check requires jevlint and the gh CLI. Run jevlint pr only in a clone you created, since it runs git fetch and calls gh. With --ast-only, changed files are not sent to a provider; a model run without that flag sends each changed file on both sides of the change.
What it helps with
- spot regressions in a pull request
- check what recent commits made worse
- locate reported issues by file and line
Example prompts for the agent
- Review pull request 42 and report only regressions.
- Check revision
abc123and show the lines where the code got worse. - Review commit
HEAD~1for regressions.
How to install review
1Plugin marketplace
/plugin marketplace add INDXDev/jevlint/plugin install jevlint@jevlint2Manually: put the files in place
.claude/commands/jevlint-review.mdThe built-in /review overrides a file with the same name, so the file is renamed. Call it with /jevlint-review. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/review.mdCall it with /prompts:review. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/review.prompt.mdManually: put the files in place
.gemini/commands/review.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about review
How do I install review in Claude Code?
Run /plugin marketplace add INDXDev/jevlint, then /plugin install jevlint@jevlint. The command file is .claude/commands/jevlint-review.md.
What does review do?
It checks a pull request or recent commits using AST metrics, then reports only regressions with file and line references.
What does review need to check a pull request?
The jevlint command and the gh CLI are required. Run jevlint pr in a clone you created; it invokes git fetch and gh.
Source text
review.md · MIT
--- description: Review what a pull request or recent commits made worse argument-hint: "[pull request number | revision]" allowed-tools: Bash(jevlint pr:*), Bash(jevlint commits:*) --- Review what a change made worse, with AST metrics only. - If `$ARGUMENTS` is a number, run `jevlint pr $ARGUMENTS --ast-only`. This needs the `gh` CLI. - Otherwise run `jevlint commits $ARGUMENTS --count 5 --ast-only`. Report only what got worse, by file and line, and name the commit or pull request. Do not drop `--ast-only` unless the user asks: a model run sends each changed file, on both sides of the change, to the provider. Only run `jevlint pr` in a clone the user made themselves, because it runs `git fetch` and `gh`.
© INDX · MIT · INDXDev/jevlint
Similar slash commands
All slash commands for Code review and refactoring →review by other authors comes first.