The why layer of repo-native project memory: the reasoning behind a codebase as Markdown in the repo, versioned by Git, for coding agents and humans, so nothing rejected is proposed twice. No database, no daemon, no account.
C-Rank Grade: A (Welcoming) - 54/100
External PR Merge Rate: 64%
Response Time: -
First Timer Success: 100%
oliver-zehentleitner/keep-the-why 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 oliver-zehentleitner/keep-the-why 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 54.2 places oliver-zehentleitner/keep-the-why in the A tier.
The external contributor pull request merge rate for oliver-zehentleitner/keep-the-why is 63.9%, based on public PR activity from non-core contributors.
oliver-zehentleitner/keep-the-why does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
The why layer of repo-native project memory: the reasoning behind a codebase as Markdown in the repo, versioned by Git, for coding agents and humans, so nothing rejected is proposed twice. No database, no daemon, no account.
Highly welcoming maintainers in oliver-zehentleitner/keep-the-why. Prompt code reviews with positive guidance for new contributors.
Discussions in oliver-zehentleitner/keep-the-why 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/oliver-zehentleitner/keep-the-why?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 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (80% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
A Skill (Claude Code, and the open Agent Skills format generally) only loads when the model decides the current conversation matches its description — there's no cross-tool "autostart" field, and no guarantee it loads every session just because a project has Keep the Why set up. Even Claude Code's own team tracks reliable auto-invocation as an open gap: anthropics/claude-code#65371. Where this actually shows up: our own eval suite has repeatedly measured this — several cases fail simply because the skill never gets invoked for a low-signal prompt, even when a project is fully set up. See docs/evals.md and the status issue for the numbers. Where we are right now The project init wizard now asks whether to set up something stronger for this, and has the current agent check what its own platform actually supports (e.g. Claude Code has SessionStart hooks that can inject a reminder at session start) and configure that scoped to the project — rather than the skill's own instructions h
The repo now ships a local eval runner (tools/evals/) that runs every case in skills/keep-the-why/evals/evals.json against a real agent session and grades the outcome with an LLM judge. Today it drives one agent: Claude Code. The skill itself is cross-agent by design, so the obvious next step is a real compatibility matrix: the same 67 cases, the same fixtures, run against Codex CLI, Gemini CLI, Copilot CLI, and other Agent-Skills-capable tools, with pass/fail per case published per agent and version. The runner already isolates the "run an agent in this prepared repo" step, so adding an agent is mostly writing one adapter (prompt + working directory in, transcript + file changes out). What's genuinely open: Infrastructure: running N agent CLIs with N sets of credentials isn't a local-laptop job — this probably wants a cloud runner, which doesn't exist yet and isn't currently planned short-term. Judging: today the judge is a Claude call; a cross-agent matrix graded by a single vendo
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 oliver-zehentleitner/keep-the-why, 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 oliver-zehentleitner/keep-the-why acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 63.9% were successfully merged into the primary branch.
oliver-zehentleitner/keep-the-why 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 54.2 places oliver-zehentleitner/keep-the-why in the Welcoming tier.
The external pull request merge rate is 63.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
oliver-zehentleitner/keep-the-why 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 oliver-zehentleitner/keep-the-why 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.