ワンクリックでManusで任意のスキルを実行

code-review

スター1,609

フォーク625

更新日2026年3月30日 19:17

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.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

ClickHouse

ClickHouse/clickhouse-java

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

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.

このリポジトリの他の Skills

同じリポジトリ

triage-issues

ClickHouse/clickhouse-java

Analyzes a single GitHub issue at a time. Reads the description, defines labels and priority, researches additional information, and provides a short but detailed report. Use when the user asks to triage an issue, analyze a bug report, or categorize a GitHub issue.

2026-06-161.6k

update-keyword-engine-lists

ClickHouse/clickhouse-java

Update ALLOWED_KEYWORD_ALIASES in ClickHouseSqlUtils.java and ENGINE_TO_TABLE_TYPE in DatabaseMetaDataImpl.java from failing test output. Use when StatementSQLTest.testAllowedKeywordAliasesMatchSystemKeywords or DatabaseMetaDataTest.testAllTableEnginesFromSystemTableEnginesAreMapped fails.

2026-05-271.6k

name	code-review
description	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.

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.