← All features

Feature

Vim Keybindings.

Navigate lines, leave comments, and finish reviews without ever touching the mouse. Crit's keybindings are designed for developers who live in the terminal.

How it works

1

Use j/k to move between lines and blocks, n/N to jump between changes. The same motions you already know from vim.

2

Press c to open the comment form on the current line. Type your feedback, then Ctrl+Enter to submit. Press Escape to cancel.

3

Use e to edit an existing comment, d to delete it. Press f to finish the review and copy the prompt. Press t to toggle the table of contents.

4

Press ? at any time to see the full shortcut reference.

Why this matters

If you work in the terminal, switching to a mouse to click through a review breaks flow. You're already in a mental mode of reading and judging code; stopping to grab the mouse and drag through line numbers is friction that adds up across a long review session.

Crit's keyboard navigation lets you move line by line with j/k, open a comment form with c, and submit — without touching the mouse at all. For developers who spend most of the day in Neovim or a terminal multiplexer, this makes Crit feel like it belongs in the same environment rather than being a browser tool you have to context-switch into.

Finishing a review is also a keyboard action. When you're done, press f and the review closes. The whole loop, from opening Crit to handing off to the agent, can stay entirely keyboard-driven.

How Crit compares

Web-based review tools like GitHub's PR interface and CodeRabbit's dashboard are mouse-first. There are browser extensions that add some keyboard navigation to GitHub reviews, but they're patchy and don't extend to tools outside of GitHub. Crit's keybindings are built in from the start, not bolted on.

Try it out

Install Crit and start reviewing agent output in seconds.

$ brew install tomasz-tomczyk/tap/crit
then run
$ crit or crit plan.md

Or download a pre-built binary from GitHub Releases.

More features