axrl-review-staged-changes

name	axrl-review-staged-changes
description	Review git-staged changes (a specific file if given, otherwise all staged files) for correctness bugs, coding-style and codebase-consistency issues, and suggestions for modularization, maintainability, efficiency, and readability. Report findings without applying fixes unless the user asks.
argument-hint	Optional file path to narrow the review; default is all staged files
user-invocable	true

axrl-review-staged-changes

Use this skill to produce a focused review of the code the user is about to commit.

Defaults

• Review git diff --cached only. Do not review unstaged edits, committed history, or the working tree.
• If the user provides a file path, scope the diff to that path: git diff --cached -- <path>.
• Do not edit code. Report findings and let the user decide. Only apply a fix when the user explicitly asks.
• Read the full file around each changed hunk before flagging an issue; a line can look wrong in isolation and be correct in context.
• Match the reviewed file's existing conventions. Don't invent house style; infer it from the surrounding code.
• Keep the report short; group findings by severity so the user can skim.

Workflow

1. Run git diff --cached (scoped to <path> if provided). If the diff is empty, say so and stop.
2. For each changed file, read the current file state (not just the diff hunks) to understand surrounding code and naming conventions.