Code Review Agent Skill

by langfuse

Review Langfuse code changes for correctness, regressions, and best practices.

2k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

32482

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/langfuse/langfuse --skill code-review

What comes with it

6 186 bytes besides the instruction

references/review-checklist.md

The instruction itself

5 sections, as written by the author

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, or touches secrets, RBAC, or redirect handling, also use

the shared security-review skill. Run its

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. 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.

Other skills for the same job

different authors, same section of the catalogue

Receiving Code Review

by ZhanlinCui

×7

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

2k tokens

Requesting Code Review

by ZhanlinCui

×6

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

Comprehensive GitHub code review with AI-powered swarm coordination

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens

How to use it

Copy the folder

Take langfuse/code-review from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.