Review Steps

1. Confirm the reviewer

If the user is not an assigned reviewer, ask whether to continue. Review only an open pull request or merge request.

2. Prepare the review

1. On GitHub, use gh pr diff and gh pr view when the pull request number is known. On GitLab, use glab mr diff and glab mr view when the merge request number is known.
2. The working directory must be the target repository. If it is not, ask the user to clone it.
3. Update the local base branch and head branch.
4. Skip the review when this skill already reviewed the current head commit. Review again when that commit has changed.
5. Read changed files and the code they call or that calls them. Leave the rest of the repository unread.
6. Do not modify code.
7. Do not open credential or secret files.

3. Verify the changed behavior

When the pull request or merge request states its intent, find where the change misses that intent: a stated case left unhandled, or behavior that contradicts the intent. Trace the new path for wrong results, dropped errors, and broken callers. Follow a call outside the diff when the diff can trigger a bug there.