Ultra Review

Produce a super-detailed, evidence-backed code review. Default scope is current git changes. If the user names a path, module, feature, package, or concern, review that target instead.

This skill is read-only unless the user explicitly asks to apply fixes.

Non-Negotiable Setup

Complete these before writing findings. Skipping them is a failed review.

1. Establish scope

Git-diff mode (default) when the user does not name a target:

1. Inspect status, staged diff, unstaged diff, and (when useful) commits ahead of the tracked base branch.
2. Prefer reviewing the full dirty worktree relevant to the ask; if only staged or only unstaged is intended and unclear, state the assumption and proceed.
3. Ignore unrelated dirty files only when the user scopes them out or they are clearly noise (generated lock churn, local env, etc.) — call out exclusions.

Targeted mode when the user points at code: