a code review TUI with vim keybindings
C-Rank Grade: S (Elite) - 70/100
External PR Merge Rate: 78%
Response Time: -
First Timer Success: 82%
agavra/tuicr has a recorded first-timer success rate of 81.6%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in agavra/tuicr respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 70.3 places agavra/tuicr in the S tier.
The external contributor pull request merge rate for agavra/tuicr is 78.4%, based on public PR activity from non-core contributors.
agavra/tuicr currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in agavra/tuicr. Prompt code reviews with positive guidance for new contributors.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/agavra/tuicr?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 17:00 UTC (17:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 21:00 to 01:00 UTC (21:00 - 01:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (35% approval). Keep your diff compact for rapid review.
Hi We currently have a single project where we have chosed to add a quite large, but generated .js file to git. But if changes occur to this file, tuicr simply stalls up trying to calculate syntax highlighting for this file. We can now, ignore this by creating a filter on command line with -p which filters out the troublesome file, but this is quite a hassle. It could therefore be great if tuicr honored the linguist-generated=true statement in .gitattributes and simply filters out those files from the PR.
Issue created with the assistance of Claude Opus 5. Summary Once a review session accumulates enough comment text, the whole TUI becomes sluggish. This is not limited to typing a reply - scrolling, navigation, and general redraw are all affected, and the cost is paid for comments that are scrolled far off screen. Comment bodies are re-highlighted through syntect's Markdown grammar on every render frame, with no memoization, and the renderer's viewport culling does not cover the comment branch. So per-frame cost grows with the total amount of comment text in the session rather than with what is visible. Symptoms Scrolling and navigation become visibly sluggish across the whole diff, not only near a large comment. Typing in the comment box is the worst case, because comment-input mode disables viewport culling entirely. Deleting large comments improves responsiveness incrementally, and the improvement tracks how much total comment text was removed. Measurements Bodies were posted with t
I find that I use Forgejo more and more besides the two large ones, so support would be much appreciated.
our CLI is a bit buggy (e.g. -version is ignored instead of failing when --version is what it should be). we also don't have proper long/short support etc... earlier I wanted to keep it simple without adding dependencies but it's grown quite a bit so we should migrate to clap.
it seems like unknown keys cause all other config keys to be ignored. We should consider just logging the failure and ignoring only unknown keys. I'll create a ticket for this as a follow-up since it doesn't look like it's super straightforward. Originally posted by @agavra in #162 (comment)
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to agavra/tuicr, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of agavra/tuicr acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 78.4% were successfully merged into the primary branch.
agavra/tuicr has a recorded first-timer success rate of 81.6%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 70.3 places agavra/tuicr in the Elite tier.
The external pull request merge rate is 78.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, agavra/tuicr currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for agavra/tuicr are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.