SKILL·82C069

crit

Name: crit
Author: tomasz-tomczyk

tomasz-tomczyk

更新日 27 days ago

3 閲覧

979

GitHubで表示

開発general

について

Critスキルは、コード変更、計画、ライブWebページ、またはローカルファイルに対するインラインコメントを通じて、構造化されたコードレビューフィードバックを提供します。ファイル、ディレクトリ、URL、GitHub PR、またはコミット範囲に対して、モード指定を必要とせずに自動的にレビューモードを検出します。開発者は、コードレビューを依頼する際、差分を分析する際、または実行中のWebアプリケーションを評価して実用的なフィードバックを得る際に、このスキルを使用すべきです。

クイックインストール

Claude Code

推奨

メイン

npx skills add tomasz-tomczyk/crit -a claude-code

プラグインコマンド代替

/plugin add https://github.com/tomasz-tomczyk/crit

Git クローン代替

git clone https://github.com/tomasz-tomczyk/crit.git ~/.claude/skills/crit

このコマンドをClaude Codeにコピー＆ペーストしてスキルをインストールします

ドキュメント

Review with Crit

Review and revise code changes, plans, live pages (running dev servers, staging URLs), or local HTML files using crit for inline comment review.

Step 1: Pass arguments to `crit`

The CLI auto-detects the review mode from its arguments. Do not ask the user which mode to use. Pass $ARGUMENTS through:

crit $ARGUMENTS               # file, dir, URL, .html — CLI auto-detects mode
crit --pr <num|url>            # GitHub PR (range mode)
crit --range <base>..<head>    # commit range (range mode)
crit                           # no args → branch diff

If no arguments, check conversation context:

A plan file was written earlier in this conversation → crit <plan-file>
Otherwise → bare crit (branch diff)

<important if="the user wants to open the review from another device — e.g. a phone over Tailscale"> Keep crit on loopback and reverse-proxy in. Same Step 1 args still apply (file, bare `crit`, etc.):

crit --public-url "https://<machine>.ts.net" --allow-unauthenticated-network --no-open [args…]
# then: tailscale serve --bg --https=443 http://127.0.0.1:<port>

--public-url only changes the URL crit prints — it does not expose the server.
--allow-unauthenticated-network is required with --public-url (even on loopback) and with any non-loopback --host. Crit has no auth: anyone who can reach the URL can read the repo and post comments that may trigger agents. Confirm the user wants that blast radius.
Do not bind --host to a Tailscale/LAN IP — proxy with tailscale serve (or an SSH tunnel). Get <port> from crit's startup output, or fix it with -p. Relay the URL crit prints (the public one), not localhost. </important>

Step 2: Launch crit and block until review completes

CRITICAL — you MUST run this step. Do NOT skip it. Do NOT proceed without it.

Run crit in the background using run_in_background: true:

crit <plan-file>   # specific file
crit               # git mode

If a crit server is already running from earlier in this conversation, crit automatically connects to it. Starting from scratch, it spawns the daemon, opens the browser, and blocks until the user clicks "Finish Review".

crit prints the review URL on startup (e.g. Started crit daemon at http://localhost:<port>). Relay it verbatim:

"Crit is open at http://localhost:<port>. Leave inline comments, then click Finish Review."

Do NOT proceed until crit completes. Do NOT ask the user to type anything. Do NOT read the review file early. Wait for the background task to finish — that is how you know the human is done reviewing.

Step 3: Read the review output

When crit completes, read stdout and follow its instructions. Check stderr for approved: true or approved: false.

<important if="a comment has a quote, anchor, or drifted field"> - `quote`: the specific text the reviewer selected — focus your changes on the quoted text rather than the entire line range - `anchor`: use it to locate the current position of the content; line numbers may be stale after edits - `drifted: true`: original content was removed or heavily rewritten — line numbers are approximate at best </important>

Fallback (mid-round re-entry, plan hooks, or headless workflows): crit comments / crit comments --json. Use crit comments --plan <slug> for plan-mode reviews.

Step 4: Address each review comment

For each unresolved comment:

Understand what the comment asks for
If it contains a suggestion block, apply that specific change
Revise the referenced file (plan or code file from the diff) using Edit
Reply with what you did: crit comment --reply-to <id> --author 'Claude Code' '<what you did>' (reply bodies support markdown)
Do not pass --resolve. Resolving is the reviewer's call. Only add --resolve if the user explicitly asks.

Editing the plan file triggers Crit's live reload — the user sees changes in the browser immediately.

<important if="you are replying to multiple comments at once"> Use `--json` for a single bulk call instead of one invocation per comment:

echo '[
  {"reply_to": "c_a1b2c3", "body": "Fixed"},
  {"reply_to": "c_d4e5f6", "body": "Refactored as suggested"}
]' | crit comment --json --author 'Claude Code'

</important>

Step 5: Signal completion and start next round

CRITICAL — you MUST run this step. Do NOT skip it. Do NOT proceed without it.

The finish prompt on stdout includes the command to run again — use it to start a new round.

On subsequent calls, crit automatically signals round-complete first, then blocks until the next "Finish Review" click.

Tell the user: "Changes applied. Review the diff in your browser and click Finish Review when ready."

Do NOT proceed until crit completes. When it does, return to Step 3. If the user finishes with zero comments, the review is approved — stop the loop and proceed.

crit share <file>

Always relay the full output to the user — copy the URL (and QR code if --qr was used) directly into your response. Don't make them dig through tool output.

To remove a shared review:

crit unpublish [file...]

</important> <important if="you are about to add --qr to a share command"> Only use `--qr` in real terminal environments with monospace rendering. Skip it in mobile apps (Claude Code mobile) or web chat UIs — Unicode block characters won't render.

crit share --qr <file>

</important>

GitHub リポジトリ

tomasz-tomczyk/crit

パス: integrations/claude-code/skills/crit

agentic-codingai-agentsai-toolsclicode-reviewdeveloper-tools

FAQ

よくある質問

crit Skillとは何ですか？

crit はtomasz-tomczyk が作成した Claude Skillです。Skillは、Claudeが必要に応じて読み込む指示とリソースをまとめ、追加の指示なしで crit に関連するタスクを実行できるようにします。

crit をインストールするには？

このページのインストールコマンドを使用してください。crit をプラグインとして Claude Code に追加するか、リポジトリを skills ディレクトリにクローンし、Claudeを再起動してSkillを読み込みます。

crit はどのカテゴリに属しますか？

crit は開発カテゴリに属します。

crit は無料で利用できますか？

はい。crit は AIMCP に掲載されており、無料でインストールできます。