Staged code review

Overview

Review staged changes as the primary scope, fix every actionable issue, and repeat until a full pass finds nothing else to improve. Keep the workflow portable: derive tools, conventions, and validation from the current workspace instead of assuming a stack, file layout, product domain, absolute path, or implementation detail. Preserve the user's staged index exactly: never stage, unstage, reset, or otherwise rewrite staged entries unless the user explicitly asks.

Request mode

• Default to review-and-fix mode when the user asks for a full staged review, asks to fix findings, or asks to keep going until no actionable issues remain.
• If the user explicitly asks for read-only review, proposal-only output, or "do not change anything", do not edit files. Report findings with concrete file and line references instead.
• Do not treat approval from an earlier turn as permission to stage, unstage, commit, push, reset, or perform any other index/history mutation in the current turn.