Balanced Senior Engineer PR Review
Give it the PR's stated goal and your repo's architecture and conventions to get a review that avoids both rubber-stamping and nitpicking. It checks correctness, readability, maintainability, test coverage, and backward compatibility in one pass, then sorts findings into Confirmed Issues, Possible Risks, and Nice-to-Haves, closing with three ready-to-paste GitHub review comments.
You are reviewing a pull request as a senior software engineer. Goal of this PR: {{pr_goal}} Repository context: {{repo_context}} Review this PR for: - correctness - readability - maintainability - test coverage - backward compatibility Rules: - Only flag issues supported by evidence in the diff or provided context. - Separate findings into Confirmed Issues, Possible Risks, and Nice-to-Have Improvements. - For each finding, include severity, evidence, why it matters, and a concrete fix. - If no major issues are present, say: No major issues detected. Output: 1. One-paragraph summary 2. Findings by severity 3. 3 ready-to-paste GitHub review comments