Your feedback loop with the agent
C-Rank Grade: S (Elite) - 71/100
External PR Merge Rate: 92%
Response Time: 4d
First Timer Success: 70%
tomasz-tomczyk/crit has a recorded first-timer success rate of 70.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in tomasz-tomczyk/crit respond to incoming external pull requests in approximately 99.8 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.5 places tomasz-tomczyk/crit in the S tier.
The external contributor pull request merge rate for tomasz-tomczyk/crit is 92.2%, based on public PR activity from non-core contributors.
tomasz-tomczyk/crit currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in tomasz-tomczyk/crit. Maintains strict focus on technical quality and test standards.
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/tomasz-tomczyk/crit?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 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~67 hours (96% approval). Large PRs (>500 lines) take ~493 hours (42% approval). Keep your diff compact for rapid review.
Currently there's no way to hide a sidebar, need ability to swap it to hamburger to center the diff.
Hey, Have you considered adding a fuzzy search? Something like Cmd + P in GitLab or any code editor, so users can search files quickly without using the browser search. I think many people would appreciate this feature. I'd like to try adding it, but only if you think it makes sense. PS. Thank you very much for creating this tool. Since switching from Cursor to a CLI‑only Claude/Codex setup, I've needed something like this. Good job 🙇
Summary crit resolves every user-level path from os.UserHomeDir() with a hardcoded .crit prefix. There is no XDG Base Directory support and no env var to relocate the root, so ~/.crit.config.json and ~/.crit/ are the only possible locations. Grepping v0.18.2 for XDG returns zero hits across internal/, cmd/, README.md and docs/. Current paths What Path Source Global config ~/.crit.config.json internal/config/config.go:471 GlobalConfigPath() Prompt templates ~/.crit/prompts/ internal/prompt/discover.go:9 (promptsSubdir joined with home) Command hooks ~/.crit/hooks/ internal/prompt/discover.go:14 Sessions / reviews ~/.crit/sessions, ~/.crit/reviews internal/daemon/daemon.go:201,219 Plans ~/.crit/plans, ~/.crit/plan-sessions.json internal/session/plans.go:24,179 Stats ~/.crit/stats.json internal/session/stats.go:42 Exports ~/.crit/exports internal/github/push_buckets.go:326 The output config key can move the review data root, but prompt/hook discovery calls DiscoverPr
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 tomasz-tomczyk/crit, 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 tomasz-tomczyk/crit acknowledge new external contributions in approximately 4 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 92.2% were successfully merged into the primary branch.
tomasz-tomczyk/crit has a recorded first-timer success rate of 70.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~4 days+. 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.5 places tomasz-tomczyk/crit in the Elite tier.
The external pull request merge rate is 92.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, tomasz-tomczyk/crit 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 tomasz-tomczyk/crit 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.