What it actually does
Reviewing a large pull request in a browser is a bad experience: you lose your place, the diff paginates, and you cannot use the editor motions your hands already know.
tuicr (pronounced "tweaker") puts the whole review in the terminal. A GitHub-style continuous diff streams every changed file in one scroll. You leave PR-style comments at line, range, file, or review level. Review progress is tracked at file or hunk granularity and persists across sessions, so you can stop halfway through a 40-file review and come back without losing your place.
Crucially it exports somewhere real: push an actual review to GitHub, GitLab, or Bitbucket, copy structured markdown to the clipboard, or pipe to stdout. It is not a private notepad — the review lands where your team already works.
It also works with git, jj, and mercurial, and reviews uncommitted changes, commit ranges, or any remote PR. At 2,600 stars it is the smallest project in this list, and the most focused.
Who it's for
- 01
Engineers who live in the terminal and resent switching to a browser to review
- 02
Anyone who regularly reviews pull requests too large to hold in their head
- 03
Teams on GitLab or Bitbucket underserved by GitHub-centric tooling
- 04
People using jj or mercurial who find most tooling assumes git
Where it earns its keep
- Reviewing a large refactor across dozens of files without losing your place
- Reviewing your own uncommitted changes before opening a pull request
- Producing structured review markdown to paste into any system
- Keeping review in the same environment as the code you are reading
- Pausing and resuming a long review across several sessions
Use it, or skip it
Reach for it when
- Pull requests are large enough that browser review genuinely hurts
- Your team uses GitLab or Bitbucket and tooling options are thin
- Vim keybindings are how your hands work and switching costs you
- You want review state to persist rather than restarting each time
Skip it when
- Your reviews are small and the browser is perfectly adequate
- Your team relies on browser-only features like suggested changes or threaded UI conversations
- Nobody on the team uses vim motions — the learning curve is real
- You need review analytics or policy enforcement; this is a review interface, not a platform
10 automations
Ideas, not tutorials. Each one is work a team does by hand today.
- 01Engineering
Self-review before pushing
Review your own uncommitted diff in the terminal and catch the obvious problems before a teammate sees them.
- 02Engineering
Large refactor review sessions
Track progress at hunk level across a multi-day review of a big migration, resuming exactly where you stopped.
- 03Engineering
Agent diff review
Review the output of an autonomous agent run in the terminal before any of it reaches a pull request.
- 04Operations
Structured review export
Pipe markdown review output into your own tooling to track findings over time.
- 05Engineering
Cross-platform review standard
Use one review interface across GitHub, GitLab, and Bitbucket repos instead of three different UIs.
- 06Engineering
Offline review
Review a commit range on a flight and push the completed review when you reconnect.
- 07Operations
Review-load balancing
Export review output to a shared log so leads can see who is carrying the review burden.
- 08Operations
Onboarding code reading
Have new hires walk historic commit ranges as a structured way to learn the codebase.
- 09Engineering
Release diff walkthrough
Before cutting a release, scroll the accumulated diff in one stream and note anything risky.
- 10Engineering
Pair-review over a terminal share
Run a shared terminal session so two people review the same continuous diff together.
Want one of these running by Friday?
LimeDock builds these as real workflows inside your stack — deployed to your cloud, wired into your Slack and CRM, with the code in your repo. You pay a build fee and your own API keys, nothing else.
Source
Repository stats were read from the GitHub API and reflect the last time we refreshed this entry. The editorial breakdown above is LimeDock’s own analysis — we are not affiliated with agavra.
https://github.com/agavra/tuicr