SKILL·36BB4A

crit

Name: crit
Author: tomasz-tomczyk

tomasz-tomczyk

更新于 8 days ago

883

开发general

关于

The `crit` skill provides inline code review for changes, plans, live web pages, or local HTML files, delivering structured feedback. It automatically detects review mode from arguments like files, directories, URLs, or GitHub PRs without requiring manual mode selection. Use it when you need human-like code review on diffs, running applications, or development work.

快速安装

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 wait for review completion

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

Run crit and wait until it exits:

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 command to finish — that is how you know the human is done reviewing.

While crit is still running, do not send user-facing progress updates. Treat the wait loop as internal state.

Step 3: Read the review output

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

When a comment has quote, anchor, or drifted:

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

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)
Reply with what you did: crit comment --reply-to <id> --author 'Codex' '<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 revising in plan mode"> Re-emit the revised plan inside `<proposed_plan>...</proposed_plan>` so Crit can review the new version. </important>

When replying to multiple comments

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 'Codex'

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 the background crit task completes. When it does, return to Step 3. If the user finishes with zero comments, the review is approved — stop the loop and proceed.

Sharing

If the user asks for a URL, a shareable link, or to share the review:

crit share <file>

Always relay the full output to the user — copy the URL directly into your response. Don't make them dig through tool output.

To remove a shared review:

crit unpublish [file...]

QR codes

Only use --qr in real terminal environments with monospace rendering. Skip it in mobile apps or web chat UIs — Unicode block characters won't render.

crit share --qr <file>

GitHub 仓库

tomasz-tomczyk/crit

路径: integrations/codex/skills/crit

agentic-codingai-agentsai-toolsclicode-reviewdeveloper-tools

FAQ

常见问题

什么是 crit Skill？

crit 是一个 Claude Skill，作者为 tomasz-tomczyk。Skill 将 Claude 按需加载的说明和资源打包，让 Claude 无需额外提示即可执行与 crit 相关的任务。

如何安装 crit？

使用本页的安装命令：将 crit 作为插件添加到 Claude Code，或将其仓库克隆到 skills 目录，然后重启 Claude 以加载该 Skill。

crit 属于哪个分类？

crit 属于开发分类。

crit 可以免费使用吗？

可以。crit 已收录在 AIMCP，可免费安装。