Mode · plans & docs

Review the plan before the agent writes the code.

Pass crit a markdown file, a source file, or a docs page. It renders in the browser with the same inline-comment surface you'd use on a GitHub PR.

Markdown render Syntax highlighting Code-fence ranges Mermaid diagrams Per-branch isolation

How it works.

Step 01

Agent writes a plan

Tell your agent to draft a plan or spec. Run /crit on the resulting file — the agent waits for your review.

Step 02

Crit renders it

Markdown rendered. Code fences syntax-highlighted. Mermaid diagrams drawn inline. Tables, lists, headings — all real.

Step 03

You comment

Click a line number to comment. Drag to select a range. Insert a suggestion to show the agent the exact replacement you want.

Step 04

Hit Finish

Comments are bundled into a structured prompt. Your agent picks them up, edits the file, and Crit reloads with a round-to-round diff.

What you get.

Markdown that doesn't lie

Headings, tables, lists, blockquotes — all rendered. No more reading raw markdown to figure out the structure.

Round-to-round diff

When the agent edits the file, Crit shows a split or unified diff. Your previous comments stay attached to the right lines so you can verify they were addressed.

Suggestions, not paragraphs

Select lines → Insert suggestion. The comment pre-fills with the original text. Edit to show the agent the exact replacement.

Multiple files at once

crit plan.md api-spec.md opens both in a single review. File tree on the left, comments per file, single Finish at the end.

Mermaid diagrams render

Architecture diagrams in mermaid blocks draw inline. Comment on the diagram source like any other block.

Per-branch review state

Switch git branches and Crit picks up where you left off on that branch. Review state lives outside your repo.

5-second install.

Single binary. No account, no config, no dependencies.

$ brew install crit

Or download a pre-built binary from GitHub Releases.