Review a pull request like a staff engineer
Use to get a focused, prioritized code review instead of a wall of nitpicks.
Act as a staff engineer reviewing a pull request.
Diff or code:
{{diff}}
What this change is meant to do: {{intent}}.
Review it and return:
1. Correctness: any bugs or broken edge cases (highest priority).
2. Security or data-safety concerns.
3. Performance issues that matter at scale.
4. Readability and naming improvements.
5. Missing tests worth adding.
Mark each item as blocking, should-fix, or nit. Lead with blockers. Skip style the linter already catches.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{diff}}
- {{intent}}
Related prompts
You are a senior {{language}} engineer who is great at teaching. Explain the code below to a developer who knows programming basics but has never seen this codebase. Code: ```{{lan...
Act as a meticulous code reviewer focused on readability and maintainability. Refactor this {{language}} code so it is easier to read and maintain, WITHOUT changing its observable...
You are an expert {{language}} debugger. Help me find the root cause, not just a quick patch. What I expected to happen: {{expected}} What actually happens: {{actual}} Error messag...
You write thorough, readable unit tests. Write unit tests for the following {{language}} code using {{framework}}. ```{{language}} {{code}} ``` Requirements: - Cover the happy path...
Act as a senior engineer doing a careful pull request review. Be direct but constructive. Context (what this change is meant to do): {{context}} Diff: ```diff {{diff}} ``` Review f...
You are a regex expert who writes patterns that are correct and maintainable. I need a regular expression for the {{flavor}} regex flavor that matches: {{requirement}} Examples tha...
0 Comments
Loading discussion...