code-review

A checklist and set of guidelines for reviewing code changes, including project structure, database access, and implementation practices.

In plain words
What is it for?
Use it to review code against task requirements, dependencies, architecture conventions, database patterns, and design principles.
Why use it?
It helps reviewers assess changes consistently, understand their context, record clear feedback, and confirm that fixes address all comments.

Cursor rule

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.

agentmods
npx agentmods add rules/squirrelogic/cursor-rules/code-review
Clone the repo
git clone --depth 1 https://github.com/squirrelogic/cursor-rules
Per session 1,630 This file is loaded in full into every session.
When invoked 1,630 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.01630 $0.01630
Opus 5 $0.00815 $0.00815
Sonnet 5 $0.00326 $0.00326
Haiku 4.5 $0.00163 $0.00163

Measured yesterday against content hash 66d9b2e4ec04, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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.

nextjs/code-review.mdc · 289 lines

How it starts

The opening of the file, as written. The whole thing — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Code Review Guidelines

Review Process

  • Before Starting Review:

    • Check task requirements and acceptance criteria
    • Review related tasks and dependencies
    • Understand the context of the changes
  • During Review:

    • Follow checklist systematically
    • Document findings clearly
    • Provide constructive feedback
    • Reference specific rules when applicable
  • After Review:

    • Verify fixes address all comments
    • Check if changes require task updates
    • Update documentation if needed

Review Checklist

Architecture & Structure

// ✅ DO: Proper server action structure
// app/actions/organization/create.ts
'use server'
import { createOrganization } from '@/lib/data/mutations/organizations'

// ❌ DON'T: Mix concerns
'use server'
import { db } from '@/db'
// Direct database operations in server action
  • Next.js 15 app directory structure
  • Server actions in app/actions/
  • Database operations in lib/data/{queries,mutations}/
  • shadcn/ui component patterns
  • SOLID principles adherence
  • Clean data access patterns

Database & Data Layer

// ✅ DO: Use Drizzle migrations
// db/migrations/0001_initial.ts
import { sql } from 'drizzle-orm'

// ❌ DON'T: Manual SQL files
// migrations/manual.sql
CREATE TABLE users...
  • Generated Drizzle migrations
  • Proper RLS policies
  • Edge function security
  • PostgreSQL style compliance
  • Type-safe database operations
  • Query optimization

Server Actions & API

// ✅ DO: Proper server action
export async function createUser(input: CreateUserInput) {
  const result = await createUserMutation(input);
  if (result.error) {
    return { error: result.error };
  }
  return { data: result.data };
}

// ❌ DON'T: Skip validation/typing
export async function createUser(formData: any) {
  const user = await db.users.create(formData);
  return user;
}
  • 'use server' directive present
  • Abstracted database operations
  • Comprehensive error handling
  • Zod schema validation
  • Proper async patterns
  • Appropriate response handling

Read the full file on GitHub · 289 lines

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.

  1. yesterday First seen · 289 lines · 1,630 tokens per session scan A 66d9b2e4ec04

Subscribe to this mod's changes

code-review is a cursor rule published in the GitHub repository squirrelogic/cursor-rules (20 stars, last pushed 1y ago), licensed MIT. It adds 1,630 tokens to every session, about $0.0081 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-30.