
Code Review
- 3 installs
- 1.6k repo stars
- Updated August 4, 2026
- clickhouse/clickhouse-java
Review clickhouse-java changes for correctness, compatibility, API stability, and missing tests.
About
Reviews changes in the clickhouse-java repo for correctness, compatibility, API stability, and missing tests. A developer uses it when reviewing pull requests, commits, diffs, or patches.
- Focuses on API stability and compatibility
- Flags missing test coverage
Code Review by the numbers
- 3 all-time installs (skills.sh)
- Ranked #923 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/clickhouse/clickhouse-java --skill code-reviewAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 3 |
|---|---|
| repo stars | ★ 1.6k |
| Last updated | August 4, 2026 |
| Repository | clickhouse/clickhouse-java ↗ |
What it does
Review clickhouse-java changes for correctness, compatibility, API stability, and missing tests.
Files
Code Review
Required context
Before reviewing, read:
AGENTS.mddocs/ai-review.md
If the review touches client-v2 or jdbc-v2, also read:
docs/features.md
Review workflow
1. Identify the changed module and any compatibility-sensitive surfaces. 2. Check correctness, regressions, API and behavior stability, JDBC or R2DBC semantics, and missing focused tests before style suggestions. 3. Use common Java and driver behavior as a comparison aid, but preserve existing project behavior unless the change is intentionally user-visible. 4. 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.