How to review Cursor-generated code

1// In Cursor's diff view, check for:
2// 1. RED LINES: Code that was deleted but should not have been
3//    - Existing error handling removed
4//    - Comments or documentation stripped
5//    - Working code replaced entirely
6// 2. GREEN LINES: New code that looks suspicious
7//    - Hardcoded values (URLs, credentials, magic numbers)
8//    - Missing error handling (no try/catch on async)
9//    - Imports from packages not in your package.json
10//    - console.log statements left in production code

1// Cursor Chat prompt (Cmd+L, Ask mode):
2// @git Review all uncommitted changes. For each modified
3// file, check for:
4// 1. Missing error handling
5// 2. Hardcoded values that should use config
6// 3. Imports that reference non-existent modules
7// 4. Security issues (SQL injection, XSS, exposed secrets)
8// 5. Functions without return types
9// 6. Dead code or unused imports
10// Report issues by file with severity (High/Medium/Low).

1---
2description: Pre-commit review checklist
3globs: ""
4alwaysApply: false
5---
6
7## Pre-Commit Review Checklist for AI Code
8Before committing, verify:
9
10### Correctness
11- [ ] All imports resolve to existing modules
12- [ ] Return types match the function contract
13- [ ] Edge cases handled (null, empty array, zero)
14- [ ] Async functions have try/catch or .catch()
15
16### Security
17- [ ] No hardcoded secrets, URLs, or API keys
18- [ ] SQL queries use parameterized statements
19- [ ] User input is validated/sanitized
20- [ ] No eval() or innerHTML with user data
21
22### Quality
23- [ ] No console.log in production code
24- [ ] No unused variables or imports
25- [ ] Function names match their behavior
26- [ ] Comments are accurate (not stale)

1// BugBot automatically reviews when you push to a branch.
2// To manually trigger a review in Cursor:
3// 1. Commit your changes to a feature branch
4// 2. Push to remote: git push origin feature-branch
5// 3. BugBot scans the diff against main
6// 4. Issues appear with confidence ratings
7// 5. Click 'Fix in Cursor' for one-click fixes
8//
9// BugBot Autofix has a 35%+ merge rate — it can
10// fix many issues automatically.

1// Quick sanity checks:
2// 1. Does the code compile? npx tsc --noEmit
3// 2. Do tests pass? npm test
4// 3. Does it work in the browser/API?
5// 4. Does the git diff look reasonable for the task?
6//    (small task = small diff, big diff = suspicious)
7
8// If the diff is unexpectedly large:
9// Cursor Chat: @git Why are there changes in 15 files
10// when I only asked to update the UserProfile component?
11// List all files that changed and explain each change.