Code Review

Use this skill when the task is to review code changes rather than implement a feature.

Start Here

Read references/review-checklist.md for the repo's canonical review rules.
Read root AGENTS.md and the nearest package AGENTS.md for the files under review.
If the review touches ClickHouse, also use the shared clickhouse-best-practices skill.
If the review touches backend code, also use the shared backend-dev-guidelines skill where relevant.
If the change accepts a user-supplied URL, adds outbound HTTP, introduces a new integration, touches secrets, RBAC, redirect handling, product analytics, browser monitoring, or session replay, also use the shared security-review skill. Run its references/checklist.md before signoff.

Focus on:

correctness bugs
behavioral regressions
security and tenant-isolation risks
performance issues with real impact
missing or weak tests for risky changes
Before calling coverage missing, identify the unique regression each proposed test catches. Do not ask for one whose only assertion would restate the diff — a spacing value, a label — because it costs a file and proves nothing. Prefer merging into the closest existing suite. Flag repeated tests of the same predicate across layers unless each proves a distinct transport, projection, or execution boundary.

Findings first, ordered by severity
File and line references for each finding
Short summary only after findings
If no findings, say so explicitly and mention any residual risk or coverage gaps

Use references/review-checklist.md for Langfuse-specific checks such as:

Do not duplicate those rules in ad hoc prompts or tool-specific command files.