A skill that runs a Greptile code review on the current local Git branch and summarizes the findings. It checks the repository, CLI installation, and login before starting the review.

Use it to review unsubmitted local changes from a Git repository and inspect the results in JSON or the available agent format.

It lets you get review feedback before opening a pull request, while making missing repository access, installation, or authentication visible.

cli-review — Skill for Claude Code by pleaseai

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.

Any agent

npx skills add pleaseai/claude-code-plugins --skill cli-review

Clone the repo

git clone --depth 1 https://github.com/pleaseai/claude-code-plugins

Made for: Claude Code.

Or install greptile, the plugin that ships this one along with the rest of its 3 skills.

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/skills/pleaseai/claude-code-plugins/cli-review.svg)](https://agentmods.dev/skills/pleaseai/claude-code-plugins/cli-review)

Your own site

<a href="https://agentmods.dev/skills/pleaseai/claude-code-plugins/cli-review"><img src="https://agentmods.dev/badge/skills/pleaseai/claude-code-plugins/cli-review.svg" alt="Measured on agentmods" height="20"></a>

Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 524 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod 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.1	$0.00061	$0.00524
Opus 5	$0.00030	$0.00262
Sonnet 5	$0.00012	$0.00105
Haiku 4.5	$0.00006	$0.00052

Measured today against content hash 56a93ea9d5da, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade C, and why

cli-review scanned grade C with 2 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 today.

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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

curl -fsSL "https://greptile.com/cli/install" | sh

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

allowed-tools: Bash(git:*) Bash(greptile:*) Bash(command:*) Bash(curl:*) Bash(npm:*)

Origin

This is a copy

100% identical to cli-review — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/greptile/.agents/skills/cli-review/SKILL.md · 95 lines

What it actually says

CLI Review

Run a Greptile review from the local checkout and summarize the findings.

Instructions

1. Confirm repository context

Start from the current repository root:

git rev-parse --show-toplevel

If the command fails, tell the user that the Greptile CLI review must be run from a git repository.

2. Check for the Greptile CLI

Check whether greptile is installed:

command -v greptile

If it is missing, do not install it automatically. Ask the user for permission, then show the recommended install command:

npm i -g greptile

If npm is unavailable, offer the shell installer fallback:

curl -fsSL "https://greptile.com/cli/install" | sh

After installation, re-run command -v greptile.

3. Ensure authentication

Check the signed-in account:

greptile whoami

If the CLI reports that authentication is missing, run:

greptile login

Wait for the user to complete the login flow before continuing.

4. Run the review

Prefer JSON output:

greptile review --json

If JSON output is unsupported or fails with a usage error, fall back to:

greptile review --agent

Do not hide the raw command failure if both commands fail. Summarize the failing command and the next action the user needs to take.

5. Summarize results

Parse JSON output when available and report:

Review status
Number of findings
Highest severity findings first
Files that need edits
Suggested next command or fix path

When output is plain text, preserve the same structure as much as possible. Keep the summary concise and focused on actionable findings.

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.

today First seen · 95 lines · 61 tokens per session scan C 56a93ea9d5da

Subscribe to this mod's changes

cli-review is a skill published in the GitHub repository pleaseai/claude-code-plugins (13 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 524 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). It is 100% identical to cli-review, differing in 0 lines, and is treated as a copy.

Code review Git and workflow

review-implement-phase

Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.

prisma/orm · 38 tokens

engram-branch-pr

PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.

Gentleman-Programming/engram · 37 tokens

verify-behavior

Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…

nicknisi/dotfiles · 68 tokens

github-contributor

End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…

daymade/claude-code-skills · 133 tokens

revdiff

Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…

umputun/revdiff · 248 tokens

write-pr

Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.

tldraw/tldraw · 53 tokens

cli-review