Review PR

Overview

Analyze and explain a pull request to help me review it effectively. Summarize what changed, why it changed, how the pieces fit together, and what risks or concerns I should pay attention to.

Inputs I May Provide

• PR number
• Branch name
• Ticket description or acceptance criteria (optional)

Behavior

• Start with a clear, concise explanation of the PR in plain language.
• Explain how the main files and changes relate to each other.
• Highlight intent and flow before implementation details.
• Be critical and skeptical, not polite.
• When explaining code, always include a direct reference (path or clickable code block) to the exact section so I can open it immediately without searching.