review-diff

Present a git diff to the user for inline annotation via the ai-review UI. Use when you want to review code changes before committing or requesting review.

Jump to install

Repository: jackfranklin/dotfiles
Last source activity: June 27, 2026 at 22:01
Detected SKILL.md language: English
Stars: 254
Forks: 33

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/jackfranklin/dotfiles --skill review-diff

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

disable-model-invocation	true
name	review-diff
description	Present a git diff to the user for inline annotation via the ai-review UI. Use when you want to review code changes before committing or requesting review.

You are presenting a git diff for human review using the ai-review CLI.

Steps

Get the diff you want to review. For staged changes use git diff --staged; for all uncommitted changes use git diff HEAD; for a specific range use git diff <base>..<head>. Note: Run git add -N . first to include untracked files in the diff. This records the intent to add the files, making them visible to git diff without fully staging them.

Run the CLI, piping the diff to stdin:

git diff HEAD | node ~/git/ai-review-plan/dist/cli.js diff --title "<short task-specific title>" --theme <dark|light>

Use --theme light unless the user has expressed a preference for dark mode.

Once the CLI launches, check its initial output (e.g. Opening http://localhost:<port>) and tell the user what port the review is active on. Wait for the CLI to exit. It blocks until the user submits their review.
Check the exit code and stdout:
- Exit 0 (Approved): The user approved the diff. Address any inline comments in code, then proceed.
- Exit 1 (Changes Requested): The user requested changes. Do not commit or push. Show the user the comments from stdout, address them in code, and offer to run another review pass.
The stdout always begins with ## Review: APPROVED or ## Review: CHANGES REQUESTED, followed by any comments as a numbered list. Read each comment carefully.

Notes

Always pass --title. Derive it from the branch name or the work being done (e.g. "Auth middleware changes", "Dark mode CSS") — never use a generic title like "Diff review".
Always pass --theme. Default to light; switch to dark if the user has indicated a preference.
If the diff is very large (hundreds of files), warn the user before opening and offer to scope it to specific paths: git diff HEAD -- src/.

review-diff

Source facts

Install options

Review the source files

More from this repository

Steps

Notes

Steps

Notes

More from this repository