Dynamic Intent Resolution Grounding Engine
C-Rank Grade: S (Elite) - 73/100
External PR Merge Rate: 96%
Response Time: 8d
First Timer Success: 85%
dirge-code/dirge has a recorded first-timer success rate of 84.6%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in dirge-code/dirge respond to incoming external pull requests in approximately 202.3 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 73.2 places dirge-code/dirge in the S tier.
The external contributor pull request merge rate for dirge-code/dirge is 96.0%, based on public PR activity from non-core contributors.
dirge-code/dirge currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in dirge-code/dirge. 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/dirge-code/dirge?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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~131 hours (96% approval). Large PRs (>500 lines) take ~971 hours (43% approval). Keep your diff compact for rapid review.
I would like for dirge to support a workflow similar to https://omo.dev/, specifically one where an agent is designated a planner that can only write down a plan that the user manually read and on manual approval fire a orchestrator agent that read the plan and delegate the implementation to individual parallel agents
This would be nice for consumers so they don't have to build the package from scratch. You can add this to flake.nix and consumers will be prompted to accept it (or via --accept-flake-config). Example: https://github.com/willruggiano/neovim.drv/blob/main/flake.nix#L36-L45 You can then add a github CI workflow that pushes to cachix on push/release/whenever you want.
I've enabled chatgpt codex and logged in successfully. But when i try to run a plan or any other prompt I get the screenshot attached.
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 dirge-code/dirge, 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 dirge-code/dirge acknowledge new external contributions in approximately 8 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 96.0% were successfully merged into the primary branch.
dirge-code/dirge has a recorded first-timer success rate of 84.6%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~8 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 73.2 places dirge-code/dirge in the Elite tier.
The external pull request merge rate is 96.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, dirge-code/dirge currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for dirge-code/dirge 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.