PR Walkthrough

Help the user understand a pull request or branch diff like a senior engineer walking them through it. Learning first; review notes secondary. Do not lead with findings unless they ask for a review.

For a canvas review layout, use branch-review-canvas instead.

Comparison base

• Use the branch, commit range, PR URL, or base ref the user named.
• Else compare the checked-out branch to main; if absent, try master.
• If PR metadata exists, prefer the PR's base branch.
• If the base is still unclear, ask once — do not guess silently.
• Treat the final diff as source of truth; use commit history for intent, not walkthrough order unless that tells a clearer story.

Depth modes

Default standard when unspecified.