A set of Claude Code and GitHub Copilot plugins providing the AI Literacy framework's complete development workflow — harness engineering, agent orchestration, literate programming, CUPID code review, and the three enforcement loops
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 100%
Response Time: 6d
First Timer Success: 100%
Habitat-Thinking/ai-literacy-superpowers 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 Habitat-Thinking/ai-literacy-superpowers respond to incoming external pull requests in approximately 133.7 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 59.3 places Habitat-Thinking/ai-literacy-superpowers in the A tier.
The external contributor pull request merge rate for Habitat-Thinking/ai-literacy-superpowers is 100.0%, based on public PR activity from non-core contributors.
Habitat-Thinking/ai-literacy-superpowers currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
A set of Claude Code and GitHub Copilot plugins providing the AI Literacy framework's complete development workflow — harness engineering, agent orchestration, literate programming, CUPID code review, and the three enforcement loops
Collaborative maintainer environment in Habitat-Thinking/ai-literacy-superpowers. Reviews community pull requests with focus on project quality.
Discussions in Habitat-Thinking/ai-literacy-superpowers 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/Habitat-Thinking/ai-literacy-superpowers?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 10:00 UTC (10:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~87 hours (96% approval). Large PRs (>500 lines) take ~642 hours (45% approval). Keep your diff compact for rapid review.
Follow-up R3 from the microsoft/AI-Engineering-Coach exploration (docs/superpowers/explorations/2026-06-16-ai-engineering-coach-findings.md, issue #340). Suggested first build of the set — smallest, fully additive, needs no behavioural data. Idea The MS Context Health page emits an agentic-readiness checklist + scalar score. We have harness-audit-engine drift detection, but it produces a backward-looking drift report, not a forward-looking readiness view. Add a binary readiness checklist (with a small score) answering "is this workspace set up for agentic work?" Candidate checklist items (all from existing artifacts) Instruction files present and non-stub: CLAUDE.md, HARNESS.md, AGENTS.md. MODEL_ROUTING.md present with routing rules. Constraints enforced (not all unverified). Reflection loop active (recent reflections/active/ fragments). Observability snapshot fresh (< cadence threshold). Orchestrator / agent pipeline present (if applicable). Home Extend /harness-audit or /superpow
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 Habitat-Thinking/ai-literacy-superpowers, 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 Habitat-Thinking/ai-literacy-superpowers acknowledge new external contributions in approximately 5 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
Habitat-Thinking/ai-literacy-superpowers 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 ~5 days+. 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 59.3 places Habitat-Thinking/ai-literacy-superpowers in the Welcoming tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Habitat-Thinking/ai-literacy-superpowers currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for Habitat-Thinking/ai-literacy-superpowers 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.