Marketplace Framework AI-Driven Dev : Context Engineering, Plugins, Agents, Skills, Hooks, Templates, SDLC
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 54%
Response Time: -
First Timer Success: 100%
ai-driven-dev/framework has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ai-driven-dev/framework 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 65.7 places ai-driven-dev/framework in the A tier.
The external contributor pull request merge rate for ai-driven-dev/framework is 53.7%, based on public PR activity from non-core contributors.
ai-driven-dev/framework does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Marketplace Framework AI-Driven Dev : Context Engineering, Plugins, Agents, Skills, Hooks, Templates, SDLC
Strict review standards in ai-driven-dev/framework. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in ai-driven-dev/framework 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/ai-driven-dev/framework?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 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (67% approval). Large PRs (>500 lines) take ~115 hours (24% approval). Keep your diff compact for rapid review.
Description 04-spec's spec-template.md has no place for unresolved open questions (unlike prd-template.md, which has ## Open Questions). build/refine mark genuine gaps as TBD: <precise question> per references/tbd-marker.md, but with nowhere designated to put them, placement is left to the drafting agent's judgment each run — confirmed non-deterministic by two real runs on the same project: one run put 3 TBDs in ## Hard constraints (where they read as nonsense — a hard constraint can't be undecided, and it contradicts spec-validator.yml's own definition of that section: "concrete and testable, not vague"), a later run on a refined version of the same feature put the same kind of TBDs under ## Context instead. Expected behaviour spec-template.md gets a ## Open Questions section (mirroring prd-template.md). Every TBD: — regardless of which section it would eventually fill — lists there, once, deterministically. Target, Hard constraints, Non-goals, and Done-when stay 100% resolved
Problem Zed is not in the compatibility table, so a Zed user has no reason to think the framework works for them. It does: Zed reads the same context files as the tools already listed. CLAUDE.md — auto-included in every Agent Panel interaction. AGENTS.md — project-level instructions. GEMINI.md — recognised natively. AIDD writes its rules to CLAUDE.md and AGENTS.md, so Zed works out of the box today. Zed also loads Skills from ~/.agents/skills/ (global) or <worktree>/.agents/skills/ (project), following the Agent Skills specification. Scope Add a Zed row to the compatibility table. Add its install steps alongside the other tools. Acceptance criteria Zed appears in the compatibility table with its install path. The claim is verified, not assumed: install into a real Zed workspace and confirm the skills load.
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 ai-driven-dev/framework, 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 ai-driven-dev/framework acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 53.7% were successfully merged into the primary branch.
ai-driven-dev/framework has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming 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 65.7 places ai-driven-dev/framework in the Welcoming tier.
The external pull request merge rate is 53.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
ai-driven-dev/framework does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for ai-driven-dev/framework 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.