Code Review
Review Langfuse code changes for correctness, regressions, and best practices.
by langfuse · MIT
The skill
Review Langfuse code changes for correctness, regressions, and best practices.
Code Review
Use this skill when the task is to review code changes rather than implement a feature.
Start Here
- Read
references/review-checklist.mdfor the repo's canonical review rules. - Read root
AGENTS.mdand the nearest packageAGENTS.mdfor the files under review. - If the review touches ClickHouse, also use the shared
clickhouse-best-practicesskill. - If the review touches backend code, also use the shared
backend-dev-guidelinesskill 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-reviewskill. Run itsreferences/checklist.mdbefore 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
- Prisma record-not-found checks (
isPrismaRecordNotFoundError/isRecordNotFoundError, not an inlinedP2025check) - 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.
Use this skill
Connect your agent to the Skill Store MCP server and ask for it by ref: langfuse/code-review-33684333431.
Details
- Publisher
- langfuse
- Category
- Software Development › Source control & code review
- License
- MIT
- Updated
- 2026-10-19
References
More from langfuse
- Add Model Price Use when editing worker/src/constants/default-model-prices.json, packages/shared/src/server/llm/t…
- Add To Dependabot Csv Append GitHub Dependabot or Snyk/code-scanning alerts to an existing vulnerability CSV after veri…
- Agent Setup Maintenance Shared workflow for editing Langfuse's repo-owned agent setup under `.agents/`.
- Analyze Cloud Costs Analyze Langfuse Cloud infrastructure cost structure using Metabase cost marts.