MCP HubMCP Hub
SKILL·82C069

crit

tomasz-tomczyk
Updated Yesterday
866
61
866
View on GitHub
Developmentgeneral

About

The Crit skill provides structured code review feedback through inline comments on code changes, plans, live web pages, or local files. It automatically detects review modes for files, directories, URLs, GitHub PRs, or commit ranges without requiring mode specification. Developers should use it when requesting code reviews, analyzing diffs, or evaluating running web applications for actionable feedback.

Quick Install

Claude Code

Recommended
Primary
npx skills add tomasz-tomczyk/crit -a claude-code
Plugin CommandAlternative
/plugin add https://github.com/tomasz-tomczyk/crit
Git CloneAlternative
git clone https://github.com/tomasz-tomczyk/crit.git ~/.claude/skills/crit

Copy and paste this command in Claude Code to install this skill

Documentation

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:

  1. A plan file was written earlier in this conversation → crit <plan-file>
  2. 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:

  1. Understand what the comment asks for
  2. If it contains a suggestion block, apply that specific change
  3. Revise the referenced file (plan or code file from the diff) using Edit
  4. Reply with what you did: crit comment --reply-to <id> --author 'Claude Code' '<what you did>' (reply bodies support markdown)
  5. 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.

<important if="the user asks for a URL, a shareable link, or a QR code for the review"> 
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 Repository

tomasz-tomczyk/crit
Path: integrations/claude-code/skills/crit
0
agentic-codingai-agentsai-toolsclicode-reviewdeveloper-tools
FAQ

Frequently asked questions

What is the crit skill?

crit is a Claude Skill by tomasz-tomczyk. Skills package instructions and resources that Claude loads on demand, so Claude can perform crit-related tasks without extra prompting.

How do I install crit?

Use the install commands on this page: add crit to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.

What category does crit belong to?

crit is in the Development category, tagged general.

Is crit free to use?

Yes. crit is listed on AIMCP and free to install.

Related Skills

qmd
Development

qmd is a local search and indexing CLI tool that enables developers to index and search through local files using hybrid search combining BM25, vector embeddings, and reranking. It supports both command-line usage and MCP (Model Context Protocol) mode for integration with Claude. The tool uses Ollama for embeddings and stores indexes locally, making it ideal for searching documentation or codebases directly from the terminal.

View skill
subagent-driven-development
Development

This skill executes implementation plans by dispatching a fresh subagent for each independent task, with code review between tasks. It enables fast iteration while maintaining quality gates through this review process. Use it when working on mostly independent tasks within the same session to ensure continuous progress with built-in quality checks.

View skill
mcporter
Development

The mcporter skill enables developers to manage and call Model Context Protocol (MCP) servers directly from Claude. It provides commands to list available servers, call their tools with arguments, and handle authentication and daemon lifecycle. Use this skill for integrating and testing MCP server functionality in your development workflow.

View skill
adk-deployment-specialist
Development

This skill deploys and orchestrates Vertex AI ADK agents using A2A protocol, managing AgentCard discovery, task submission, and supporting tools like Code Execution Sandbox and Memory Bank. It enables building multi-agent systems with sequential, parallel, or loop orchestration patterns in Python, Java, or Go. Use it when asked to deploy ADK agents or orchestrate agent workflows on Google Cloud.

View skill