Linked-Intent Development - a SDD methodology for agentic coding
C-Rank Grade: B (Solid) - 44/100
External PR Merge Rate: 50%
Response Time: <1h
First Timer Success: -
jszmajda/lid has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in jszmajda/lid respond to incoming external pull requests in approximately 0.5 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 43.8 places jszmajda/lid in the B tier.
The external contributor pull request merge rate for jszmajda/lid is 50.0%, based on public PR activity from non-core contributors.
jszmajda/lid currently has 8 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in jszmajda/lid. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in jszmajda/lid 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/jszmajda/lid?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 & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (62% approval). Large PRs (>500 lines) take ~2 hours (22% approval). Keep your diff compact for rapid review.
We document a an AGENTS.md-native tool (Codex CLI, Zed, Amp, goose, etc.) setup in docs/setup.md § The simple path: just ship AGENTS.md, but the maintainer doesn't use an AGENTS.md-native tool (Codex CLI, Zed, Amp, goose, etc.) day-to-day — this needs field validation. If you use an AGENTS.md-native tool (Codex CLI, Zed, Amp, goose, etc.), try LID on a real task and post here: Did it work? Did the agent actually follow the workflow — walk the phases, stop for your review, write EARS specs and @spec annotations? What did you have to do to set it up, beyond what docs/setup.md says? Any evidence you can share — transcript snippets, a repo link, screenshots. Name the tool and version in your report — this issue collects reports for any tool that reads AGENTS.md natively and has no dedicated section in setup.md. Negative reports are just as valuable as positive ones — "the agent ignored the rule file entirely" is exactly what we need to know. Fixes to the setup.md entry are wel
We document a JetBrains AI Assistant setup in docs/setup.md § JetBrains AI Assistant (distinct from Junie), but the maintainer doesn't use JetBrains AI Assistant day-to-day — this needs field validation. If you use JetBrains AI Assistant, try LID on a real task and post here: Did it work? Did the agent actually follow the workflow — walk the phases, stop for your review, write EARS specs and @spec annotations? What did you have to do to set it up, beyond what docs/setup.md says? Any evidence you can share — transcript snippets, a repo link, screenshots. Negative reports are just as valuable as positive ones — "the agent ignored the rule file entirely" is exactly what we need to know. Fixes to the setup.md entry are welcome as PRs (trivial-change tier per CONTRIBUTING.md — no arrow walk needed).
We document a JetBrains Junie setup in docs/setup.md § JetBrains Junie, but the maintainer doesn't use JetBrains Junie day-to-day — this needs field validation. If you use JetBrains Junie, try LID on a real task and post here: Did it work? Did the agent actually follow the workflow — walk the phases, stop for your review, write EARS specs and @spec annotations? What did you have to do to set it up, beyond what docs/setup.md says? Any evidence you can share — transcript snippets, a repo link, screenshots. Negative reports are just as valuable as positive ones — "the agent ignored the rule file entirely" is exactly what we need to know. Fixes to the setup.md entry are welcome as PRs (trivial-change tier per CONTRIBUTING.md — no arrow walk needed).
We document a Continue.dev setup in docs/setup.md § Continue.dev, but the maintainer doesn't use Continue.dev day-to-day — this needs field validation. If you use Continue.dev, try LID on a real task and post here: Did it work? Did the agent actually follow the workflow — walk the phases, stop for your review, write EARS specs and @spec annotations? What did you have to do to set it up, beyond what docs/setup.md says? Any evidence you can share — transcript snippets, a repo link, screenshots. Continue's adapter inlines the methodology (it doesn't auto-read AGENTS.md), so drift between the rule file and AGENTS.md is a specific thing to watch for. Negative reports are just as valuable as positive ones — "the agent ignored the rule file entirely" is exactly what we need to know. Fixes to the setup.md entry are welcome as PRs (trivial-change tier per CONTRIBUTING.md — no arrow walk needed).
We document a Aider setup in docs/setup.md § Aider, but the maintainer doesn't use Aider day-to-day — this needs field validation. If you use Aider, try LID on a real task and post here: Did it work? Did the agent actually follow the workflow — walk the phases, stop for your review, write EARS specs and @spec annotations? What did you have to do to set it up, beyond what docs/setup.md says? Any evidence you can share — transcript snippets, a repo link, screenshots. Negative reports are just as valuable as positive ones — "the agent ignored the rule file entirely" is exactly what we need to know. Fixes to the setup.md entry are welcome as PRs (trivial-change tier per CONTRIBUTING.md — no arrow walk needed).
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 jszmajda/lid, 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 jszmajda/lid acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 50.0% were successfully merged into the primary branch.
jszmajda/lid has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. 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 43.8 places jszmajda/lid in the Solid tier.
The external pull request merge rate is 50.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, jszmajda/lid currently has 8 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for jszmajda/lid 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.