A checklist for reviewing code changes before approval or pull-request review. A pull request is a proposed code change that others inspect before it is merged.

Use it to review changes for bugs, unsafe input handling, missing authorization, slow query patterns, duplication, and inadequate tests.

It helps reviewers check correctness, security, performance, maintainability, and test coverage systematically.

code-review — Cursor rule for Cursor by boparaiamrit

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/boparaiamrit/skills-by-amrit

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/rules/boparaiamrit/skills-by-amrit/code-review.svg)](https://agentmods.dev/rules/boparaiamrit/skills-by-amrit/code-review)

Your own site

<a href="https://agentmods.dev/rules/boparaiamrit/skills-by-amrit/code-review"><img src="https://agentmods.dev/badge/rules/boparaiamrit/skills-by-amrit/code-review.svg" alt="Measured on agentmods" height="20"></a>

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 409 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00015	$0.00409
Opus 5	$0.00008	$0.00204
Sonnet 5	$0.00003	$0.00082
Haiku 4.5	$0.00002	$0.00041

Measured 6d ago against content hash 62fc44c85c10, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

code-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

cursor-rules/code-review.mdc · 51 lines

What it actually says

Code Review Checklist

Before Approving Any Change, Verify:

Correctness

Logic is correct (no off-by-one, race conditions, null derefs)
All code paths are handled (happy path, errors, edge cases)
Types match (no implicit conversions or any abuse)
Return values are checked
Side effects are documented or eliminated

Security

User input is validated and sanitized
SQL queries are parameterized
Auth/authz checks are present where needed
Sensitive data is not leaked in logs/responses
No hardcoded secrets or credentials

Performance

No N+1 query patterns
No unbounded loops or recursion
Pagination for list endpoints
No unnecessary re-renders (React)
Expensive operations are cached where appropriate

Maintainability

Code is readable without comments
Functions are small (< 50 lines)
Follows existing project patterns
No code duplication
Names are descriptive and consistent
Abstraction level is appropriate

Testing

Tests exist for new code
Tests cover happy path AND error paths
Tests are independent (no shared mutable state)
No test regressions

Severity Guide

🔴 Critical (must fix): Security vulnerability, data loss risk, crash
🟠 Important (should fix): Logic error, performance issue, missing validation
🟡 Suggestion (nice to have): Readability, convention, minor improvement
🟢 Praise (keep doing this): Well-written code, good patterns

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

6d ago First seen · 51 lines · 15 tokens per session scan A 62fc44c85c10

Subscribe to this mod's changes

code-review is a cursor rule published in the GitHub repository boparaiamrit/skills-by-amrit (5 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 409 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code review

code-review

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Code Review Checklist

Before Approving Any Change, Verify:

Correctness

Security

Performance

Maintainability

Testing

Severity Guide

What this file has done since we first saw it

Other cursor rules, from other repositories

clean-code-reviewer

sweep-benchmarks

code-review

ponytail

angular-20

dev-standard