Top-Down Review

Do not edit code unless the user explicitly asked to fix the findings.

Project review profile

Follow Project profile when the user asks to set up the project review profile, REVIEW.md. During a review, if the project has no profile and the review relied on project-specific checks worth recording, offer one in To discuss.

Process

1. Read Review method.
2. Determine the review range — the base and the reviewed revision — and use the same range in every later command.
   • For a branch or an MR/PR, the base is the merge base with a freshly fetched target branch, not a stale local ref. The target branch is the MR/PR target, otherwise the base branch named in REVIEW.md, otherwise the branch refs/remotes/origin/HEAD points to.
   • For uncommitted changes, the base is HEAD, and the range includes the in-scope untracked files, which git diff omits.
   • Keep a range the user defined explicitly.