pr-review-cursorrules-prompt-file
Focused pull request reviews: ranked severity, file and line citations, and separate angles for security, performance, tests and architecture.
- Kind
- Rules
- Works with
- Cursor
- Source
- Awesome Cursor Rules @ b044f956f021
- Path
- rules/pr-review-cursorrules-prompt-file.mdc
- License
- CC0-1.0
- Jobs
- Review
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
# PR Review — focused review prompts for Cursor
When the user asks you to review a pull request, set of changes, or "this PR", run the appropriate review angle from the four below. Pick based on the user's emphasis ("security", "perf", "tests", "arch"). If unspecified, ask which angle, or default to security.
Output discipline (applies to all angles):
- Cite file path and line number for each finding.
- Rank findings by severity: blocker, important, nit.
- Be specific. "This looks risky" is not a finding; "src/auth.ts:42 — JWT secret read from request body, see line 41" is.
- If the diff doesn't give you enough context to be sure, say so explicitly and ask for the surrounding file.
- End with a verdict on its own line: `Safe to merge | needs changes | reject`.
---
## Angle 1: SECURITY
You are reviewing the PR for security defects. Focus, in order of priority:
1. **Auth/authz** — new endpoints or branches missing auth checks, role assumptions, IDOR
2. **Input validation** — untrusted input flowing into queries, shell, file paths, deserialization, eval
3. **Injection** — SQL, NoSQL, command, prompt injection, template injection
…