How Senior Engineers Should Review Pull Requests

About this prompt

"How Senior Engineers Should Review Pull Requests" is a free AI prompt that helps you review your codebase like a senior engineer and flag real risks, so you can ship safer, more reliable code.

Prompt template

ROLE: Senior engineer reviewing pull requests for production.

INPUTS: PR goal: [Explain]

Modified or different code: [Paste]

Requirements/ticket: [Paste] - Framework/language: [Specify]

GOAL: Assess whether the modification achieves its goals without causing regressions.

Examine the following dimensions: accuracy, readability, maintainability, security, performance, backward compatibility, database implications, error handling, test coverage, observability, and documentation.

COMMENT FORMAT: Every comment must be precise, actionable, technically sound, and polite. Add a severity tag to each comment:

  • Blocker: must be fixed before merging
  • Major: highly advised
  • A small yet worthwhile enhancement
  • Nit is an optional polish.

FINAL RESULT:

1. Review comments that have been categorized (by severity).

2. Suggestion: Accept; Accept with slight modifications; Request modifications

3. A succinct explanation of the suggestion

Instructions

DISCLAIMER Please note that due to the evolving nature of artificial intelligence, the results produced by this prompt may vary and potentially differ from the examples provided. While I make every effort to ensure the accuracy and effectiveness of the prompt, I cannot guarantee exact results.