cr

/cr - Generic Code Review

When the user invokes /cr, review the current repository's uncommitted changes. This skill is intentionally generic: it focuses on review rules and changed code, not branch comparison or release workflow.

Project-Local Rules First

Before applying the generic checklist, look for project-specific review rules and prefer them when present.

Check likely locations:

find . -maxdepth 4 \( -path './node_modules' -o -path './.git' \) -prune -o \
  \( -path './.cursor/commands/cr.md' -o -path './.cursor/rules' -o -name 'AGENTS.md' -o -name 'CLAUDE.md' \) -print

If a project-local /cr command or review rules exist:

• Read and apply them first.
• Use generic /cr rules only as a fallback or supplement.
• In the report, state which project-local files were applied.
• If project-local rules conflict with this generic skill, project-local rules win.

Scope

Review uncommitted changes only:

git status -sb
git diff --name-status
git diff --stat
git diff
git diff --staged --name-status
git diff --staged --stat
git diff --staged
git ls-files --others --exclude-standard

Do not compare against upstream branches, merge bases, or release targets unless the user explicitly asks. If there are no staged, unstaged, or relevant untracked changes, report that there is nothing to review.

For untracked files, inspect them when they look like source, config, migration, test, or documentation files related to the change.

Language Profiles

Infer active profiles from changed files and project layout. Apply all matching profiles.

React / TypeScript Frontend

Use for ts, tsx, js, jsx, css, less, scss, route, i18n, and frontend config changes.

Focus on:

• Type safety: props, hooks, API responses, generics, casts, any, and stale interfaces.
• React behavior: hook dependencies, stale closures, memoization misuse, controlled inputs, key stability, effects with async work, and cleanup.
• Error and loading states: failed requests, empty states, retries, disabled controls, and user-facing feedback.
• Null safety: optional data, arrays, refs, DOM access, nested API fields, and conditional rendering.
• Feature flags and environment gates for new behavior.
• State consistency: React Query cache invalidation, Zustand/store updates, URL state, local storage, and cross-tab behavior.
• Layout impact: overflow, responsive behavior, fixed heights, table columns, modals, z-index, and style leakage.
• i18n: missing keys, hard-coded user-facing text, wrong locale file updates, and malformed translation keys.
• Tests: missing focused tests for changed formatting, branching, hooks, reducers, or regressions.