Pre-Commit Review

Trigger: use when the user asks for a commit-readiness review in phases (source, tests, commit-message prep).

Run phases sequentially. Do not auto-advance from one phase to the next. After each phase:

• Present findings.
• Pause for user-directed fixes/discussion.
• Continue to the next phase only when the user asks to proceed.

Phase 1: Source Review

• Start by enumerating the full current worktree (staged, unstaged, and untracked files).
• Treat the full worktree as the primary review scope, not only the most recent edits.
• Review source changes in that scope exhaustively.
• Read full files for changed files and tangentially related files as needed to validate behavior.
• Focus on bugs, regressions, race conditions, broken UX, contract breaks, and risky side effects.
• Use concrete evidence from code paths and call sites, not speculation.