Put the world's smartest AI agents & plugins in your pocket
C-Rank Grade: B (Solid) - 54/100
External PR Merge Rate: 95%
Response Time: -
First Timer Success: 100%
xiaotonng/pikiloom has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in xiaotonng/pikiloom 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.5 places xiaotonng/pikiloom in the B tier.
The external contributor pull request merge rate for xiaotonng/pikiloom is 95.0%, based on public PR activity from non-core contributors.
xiaotonng/pikiloom currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Put the world's smartest AI agents & plugins in your pocket
Collaborative maintainer environment in xiaotonng/pikiloom. Reviews community pull requests with focus on project quality.
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/xiaotonng/pikiloom?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 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 04:00 to 08:00 UTC (04:00 - 08:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (43% approval). Keep your diff compact for rapid review.
Problem When using Pikiclaw for multiple tasks, once the number of sessions exceeds ~5-10, it becomes very difficult to recall: What tasks were previously sent and whether they were valuable What the agent's feedback/results were for each task Which sessions are worth revisiting vs. which are noise This is true across both IM (Telegram/Feishu) and the dashboard — the current session list is flat and chronological with no summarization, search, or filtering. Users end up manually scrolling through conversations or the dashboard trying to piece together what happened. Why This Matters Pikiclaw encourages an async, fire-and-forget workflow — send tasks and check back later. But without a way to efficiently review past sessions, users lose track of their own work. The more productive the tool is, the worse this problem gets. Possible Directions Session summaries: Auto-generate a one-line summary for each completed session (task intent + outcome) Search/filter: Allow searching sessio
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 xiaotonng/pikiloom, 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 xiaotonng/pikiloom acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 95.0% were successfully merged into the primary branch.
xiaotonng/pikiloom has a recorded first-timer success rate of 100.0%. Repositories ranked Solid 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.5 places xiaotonng/pikiloom in the Solid tier.
The external pull request merge rate is 95.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, xiaotonng/pikiloom 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 xiaotonng/pikiloom 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.