---
name: langfuse-code-review
description: "Review Langfuse code changes for correctness, regressions, and best practices."
license: "NOASSERTION"
metadata:
  decimalai-skill-id: "853d119b-4c28-426f-a8d1-54c4c5364636"
  decimalai-version-id: "a25dd05b-500c-41bc-9465-132c5aa1635a"
  decimalai-version: "2"
  decimalai-body-sha256: "d1a23f45519e014ae220d83fccc5c6d88cbea20c59f26c10b9ad5950a3d12c12"
  decimalai-name: "langfuse/code-review"
  decimalai-format: "1"
  decimalai-invocation: "model"
  decimalai-category: "code-review"
  decimalai-source: "https://app.decimal.ai/s/langfuse-code-review@2/SKILL.md"
---
# 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`](references/review-checklist.md) for
  the repo's canonical review rules.
- Read root [`AGENTS.md`](../../../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`](../security-review/SKILL.md) skill. Run its
  [`references/checklist.md`](../security-review/references/checklist.md)
  before signoff.

## Review Priorities

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.

## Output Expectations

- 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

## Scope Guidance

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

- ClickHouse and Postgres migration expectations
- project-scoped tenant isolation checks
- API/Fern consistency
- banner-offset UI positioning
- environment variable access patterns

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