Review Changes

Review changed code with explicit severity and confidence.

Process

Follow this sequence to produce a thorough, efficient review:

1. Understand intent. Read the PR description, commit messages, linked issues, and any existing reviewer feedback. Know what the change is trying to do before judging how well it does it.
2. Load prior-feedback guidance when needed. If the review already has comments or notes, read references/reviewer-feedback.md before reviewing the diff so you can check whether that feedback still applies and how to respond to it. Treat requests to address review findings, PR feedback, review comments, requested changes, or an end-to-end review follow-up as requests to handle existing GitHub review feedback when the change is on a GitHub pull request. Collect the active comments first, track each open thread, map each still-valid concern to the relevant technical lens, and