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.

Ir a la instalación

Repositorio: jackfranklin/dotfiles
Última actividad en el origen: 27 de junio de 2026 a las 22:01
Idioma detectado de SKILL.md: inglés
Estrellas: 254
Forks: 33

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

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

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

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

Datos de origen

Opciones de instalación

Revisa los archivos de origen

Más de este repositorio

Steps

Notes

Más de este repositorio

Steps

Notes