mcpbeat

Code Review

clickhouse/code-review

Review changes in clickhouse-java for correctness, compatibility, API stability, and missing tests. Use when reviewing pull requests, commits, diffs, patches, or when the user asks for a code review.

290 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1610
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/ClickHouse/clickhouse-java --skill code-review

The instruction itself

4 sections, as written by the author

Code Review

Required context

Before reviewing, read:

  • AGENTS.md
  • docs/ai-review.md

If the review touches client-v2 or jdbc-v2, also read:

  • docs/features.md

Review workflow

  • Identify the changed module and any compatibility-sensitive surfaces.
  • Check correctness, regressions, API and behavior stability, JDBC or R2DBC semantics, and missing focused tests before style suggestions.
  • Use common Java and driver behavior as a comparison aid, but preserve existing project behavior unless the change is intentionally user-visible.
  • Report findings first, ordered by severity, then open questions or assumptions, then a brief summary.

Final response requirements

State:

  • what changed
  • whether compatibility risk exists
  • what tests were run, or why they were not run
  • whether docs should change

If no issues are found, say so explicitly and mention residual risk or testing gaps.

How to use it

Copy the folder

Take clickhouse/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.