# Crit > Review code changes, a plan, a live page (running dev server), or a local HTML file with Crit inline comments and structured human feedback. Use only when the user explicitly invokes /crit or directly asks to use Crit; a generic review request does not count. - Skill: `gabrielmoreira/crit-10` (Agent Skill) - Install (CLI): `npx skillmds@latest add gabrielmoreira/crit-10` - Raw SKILL.md: https://api.skillmd.com/api/skills/gabrielmoreira/crit-10/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Web & Frontend - Author: gabrielmoreira (https://skillmd.com/u/gabrielmoreira) - Updated: 2026-09-21 - Page: https://skillmd.com/skills/gabrielmoreira/crit-10 --- # Review with Crit This is the interactive, human-in-the-browser review cycle. Run it only after the user explicitly invokes `/crit` or directly asks to use Crit. A generic request to review code, a plan, a diff, a PR, or a page does not count. 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 # file, dir, URL, .html — CLI auto-detects mode crit --pr # GitHub PR (range mode) crit --mr # GitLab MR (range mode) crit --range .. # 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 ` 2. Otherwise → bare `crit` (branch diff) Keep crit on loopback and reverse-proxy in. Same Step 1 args still apply (file, bare `crit`, etc.): ```bash crit --public-url "https://.ts.net" --allow-unauthenticated-network --no-open [args…] # then: tailscale serve --bg --https=443 http://127.0.0.1: ``` - `--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 `` from crit's startup output, or fix it with `-p`. Relay the URL crit prints (the public one), not localhost. ## 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: ```bash crit # 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:`). Relay it verbatim: > **"Crit is open at http://localhost:. 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 ` 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) 4. Reply with what you did: `crit comment --reply-to --author 'Codex' ''` (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. Re-emit the revised plan inside `...` so Crit can review the new version. ### When replying to multiple comments Use `--json` for a single bulk call instead of one invocation per comment: ```bash 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: ```bash crit share ``` **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: ```bash 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. ```bash crit share --qr ```