Perform a scoped, cost-conscious code review using only the provided diff, selected files, or explicitly named files.
Copilot ✓Cursor —Kilo —
AuthorNeexoCore
Updated
code-reviewcost
Perform a scoped code review using minimal context.
Review only the provided diff, selected files, or files explicitly named by the user.
Do not scan the entire repository.
Focus on:
correctness
security
tenant or customer isolation
data loss
production deployment risk
missing validation
missing tests
obvious maintainability issues
Ignore:
subjective style preferences
broad refactor suggestions
generated files
build output
assets
lock files unless dependency behavior is relevant
Output:
Critical issues
Medium issues
Low-risk suggestions
Missing tests
Files that need human review
Keep the review concise.
Raw content
Copy into your project — e.g. .instructions.md, .agent.md, or SKILL.md
Perform a scoped code review using minimal context.
Review only the provided diff, selected files, or files explicitly named by the user.
Do not scan the entire repository.
Focus on:
- correctness
- security
- tenant or customer isolation
- data loss
- production deployment risk
- missing validation
- missing tests
- obvious maintainability issues
Ignore:
- subjective style preferences
- broad refactor suggestions
- generated files
- build output
- assets
- lock files unless dependency behavior is relevant
Output:
1. Critical issues
2. Medium issues
3. Low-risk suggestions
4. Missing tests
5. Files that need human review
Keep the review concise.