logo

agavra/tuicr

a code review TUI with vim keybindings

View on GitHub ↗Jump to charts ↓Open shareable report →

agavra/tuicr has 3k+ stars and 300+ forks on GitHub, is written in Rust, and was last pushed on Oct 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Type:CLI ToolCategory(s):Git & Version ControlDeveloper Tools
Added to GitGenius on September 21st, 2026
Created on January 8th, 2026
Open Issues & Pull Requests: 101 (+0)
GitHub issues: Enabled
Number of forks: 307
Total Stargazers: 3,403 (+0)
Total Subscribers: 7 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 34.2 hours
Mean response time: 16.4 days
90th percentile: 57.4 days
Tracked items: 253

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

Maintainer activity

13 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 11% of issues opened in the past year have never received a reply. 83% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "bug" is answered fastest, typically in about 9 hours, while "enhancement" waits about 2 days. 25% of tracked open issues have had no activity in three months. 75% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 72
New in 7 days: 10
Closed in 7 days: 37
Avg open age: 78 days
Stale 30+ days: 45
Stale 90+ days: 14

Recent activity

Opened in 7 days: 10
Closed in 7 days: 3
Comments in 7 days: 3
Events in 7 days: 7

Top labels

  • enhancement (62)
  • bug (43)
  • good first issue (32)
  • help wanted (12)
  • documentation (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in
Explore full issue details

Detailed Description

tuicr is a code review terminal user interface with vim keybindings.

The tool addresses the friction of reviewing code through web interfaces by providing a keyboard-driven terminal application. It integrates with version control systems to fetch pull requests and diffs, then presents them in a vim-like environment where reviewers can navigate, comment, and approve changes without leaving the terminal. The approach prioritizes keyboard efficiency and modal editing patterns familiar to vim users.

Developers who spend significant time in terminal environments and prefer vim workflows will find this tool most valuable. It suits projects where code review happens frequently and reviewers want to minimize context switching between their editor and a browser. The tool is particularly useful for those already comfortable with vim keybindings who want that same interaction model applied to the review process.

The project shows active development with regular commits addressing bug fixes and feature improvements. Work spans multiple areas including core review functionality, integration enhancements, and user experience refinements. The codebase receives consistent attention to code quality and responsiveness to issues raised by users.