| name | crit |
| description | 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. |
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 <arguments> # file, dir, URL, .html — CLI auto-detects mode
crit --pr <num|url> # GitHub PR (range mode)
crit --mr <iid|url> # GitLab MR (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)
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…]
- only changes the URL crit prints — it does expose the server.
