A memory layer for Claude Code that learns as you work. Persistent, per-context memory as plain markdown in your own git repo. No server, no telemetry.
C-Rank Grade: D (Risky) - 8/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
anshulforyou/grandma 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 anshulforyou/grandma 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 anshulforyou/grandma in the D tier.
The external contributor pull request merge rate for anshulforyou/grandma is 0.0%, based on public PR activity from non-core contributors.
anshulforyou/grandma currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Shell project in anshulforyou/grandma welcoming community pull requests and bug fixes.
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/anshulforyou/grandma?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 21:00 UTC (21:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 20:00 to 00:00 UTC (20:00 - 00:00 UTC local).
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.
docs/use-cases.md could carry a handful of concrete walkthroughs, each a real command sequence with the output you actually see. Good candidates: knitting a new sweater and onboarding a project, the everyday teach-once loop, running a watch campaign and reading the report, reviewing a distill proposal at the next launch, and turning on tab completion. Docs only, no engine changes. Match the README tone: concrete, transcript-driven, honest about the rough edges. Keep to ASCII prose and use invented names like globex or home-ops in examples, never a real company or client, since this is a clean-room and examples get copied.
There is no single place to see the state of things. grandma status should print it: each sweater with how many projects it has, how many review proposals are pending, whether memory has uncommitted changes, and which watch reports are finished but unread. Everything it needs already exists and should be reused, not rebuilt: list_scopes and project_entries for sweaters and counts, the proposals/<sweater>*.md glob that launch uses for pending proposals, git -C $ROOT status --porcelain on the markdown for the dirty check, and watches/*/report.md without a sibling .seen for unread reports. Done when the output is a compact, readable summary, the counts are right against the fixture (home-ops has one pending proposal), it runs under set -u, and test/cmd_status.sh asserts the sweater names and those counts.
Small quality-of-life command. grandma edit acme opens acme's memory folder in $EDITOR. An optional second word could open one file, like grandma edit acme facts. Notes for whoever picks this up: new lib/grandma-edit.sh plus a dispatch case. Resolve the sweater with resolve_scope_dir so a kebab name like home-ops works, and reuse the existing friendly path when the sweater does not exist. Fall back to a sane editor if $EDITOR is unset. This command ends in launching an editor, so it must honor GRANDMA_DRY_RUN=1 by printing what it would open and exiting 0, the same contract every exec path here follows. Done when it opens the right target, the dry run prints the plan without spawning an editor, and test/cmd_edit.sh checks the dry run against the kebab fixture.
Document (or build) the flow where a small team shares one scope repo: clone, load, merge policy for captures. docs/use-cases.md candidate.
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 anshulforyou/grandma, 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 anshulforyou/grandma 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.
anshulforyou/grandma 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 anshulforyou/grandma 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, anshulforyou/grandma currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for anshulforyou/grandma 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.