Intent compiler for AI agents — converges vague requests into typed IntentSpec contracts (probe, ask, or halt before routing), the input layer for routers and typed-decision models like Jev & Laya
C-Rank Grade: D (Risky) - 8/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
angel291592/Intent-Router has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in angel291592/Intent-Router 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 7.5 places angel291592/Intent-Router in the D tier.
The external contributor pull request merge rate for angel291592/Intent-Router is 0.0%, based on public PR activity from non-core contributors.
angel291592/Intent-Router currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in angel291592/Intent-Router. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in angel291592/Intent-Router focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/angel291592/Intent-Router?utm_source=github&utm_medium=badge)
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
In the 2026-09-22 Claude Code runs, the failure-behaviour question that should trigger ASK was skipped in 3-shot sampling: add-caching-explicit 1/3, two-turn 1/3, fully-specified 1/3, vague-no-ask 1/2. Rules already added (enumerate failure paths, ask-order: behaviour/contract first and internal structure never asked, excluding an option ≠ resolving an unknown) moved things in the right direction but haven't fully converged. Plan: add a positive-contrast fixture next to the §4.1 iron rule (a route.yaml/ask.yaml-style scenario showing what "fully specified" looks like), then re-verify on a clean channel (tracked in the clean-channel re-run issue).
The 2026-09-22 Claude Code runs went through a channel that forced thinking off and answered English prompts in Chinese, so the failures can't be attributed to the skill itself. The report was therefore removed from the repo and Claude Code dropped to spec-compatible (see CHANGELOG 0.2.0). The methodology and cases stay public; only the report is held back. Pending work: Re-run the full 10-case suite on an unrestricted channel (TIMEOUT is now 480s; the ungrillable case that hit the old 240s limit and was not re-run for cost reasons must be included) Confirm the fixes already in the skill (quoting hard rule, evidence token shape, ask-order rules) also converge on Claude Code On pass: delete the evals/reports/*-claude-code.md line in .gitignore, re-commit the report, restore verified in both READMEs
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 angel291592/Intent-Router, 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 angel291592/Intent-Router acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
angel291592/Intent-Router has a recorded first-timer success rate of 0.0%. Repositories ranked Risky 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 7.5 places angel291592/Intent-Router in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, angel291592/Intent-Router 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 angel291592/Intent-Router 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.