rullerzhou-afk/clawd-on-desk - Open Source PR Review Scorecard

A pixel desktop pet that watches Claude Code, Codex, Cursor & other AI coding agents — so you don't have to.

C-Rank Grade: B (Solid) - 54/100

External PR Merge Rate: 77%

Response Time: 3d

First Timer Success: 57%

Frequently Asked Questions

Is rullerzhou-afk/clawd-on-desk welcoming to first-time open-source contributors?

rullerzhou-afk/clawd-on-desk has a recorded first-timer success rate of 57.1%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in rullerzhou-afk/clawd-on-desk respond to incoming external pull requests in approximately 69.9 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 53.6 C-Rank™ score (B Tier) represent?

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 53.6 places rullerzhou-afk/clawd-on-desk in the B tier.

What is the external contributor pull request merge rate for rullerzhou-afk/clawd-on-desk?

The external contributor pull request merge rate for rullerzhou-afk/clawd-on-desk is 77.4%, based on public PR activity from non-core contributors.

Are there Good First Issues available in rullerzhou-afk/clawd-on-desk?

rullerzhou-afk/clawd-on-desk does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.

rullerzhou-afk
rullerzhou-afk/clawd-on-deskBSolid6.0k
GitHub
Back to Explorer
rullerzhou-afk

rullerzhou-afk/clawd-on-desk

6,031
BSolid(54/100)JavaScript

A pixel desktop pet that watches Claude Code, Codex, Cursor & other AI coding agents — so you don't have to.

Compare
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
8.7/10
Patience Score
8.6/10
Nitpick Rate
40%

Highly welcoming maintainers in rullerzhou-afk/clawd-on-desk. Prompt code reviews with positive guidance for new contributors.

Top PR Submission Do's

  • Follow maintainer feedback from recent PR reviews

Top PR Friction Pitfalls (Don'ts)

  • Do not ignore unresolved maintainer review comments
Response Velocity
2 days+
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
77.4%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
57.1%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
29 core
Highly collaborative maintainer core
Diagnostic Health HUD
77.4%
Merge Gauge
57.1%
1st-Timer
Community Vibe48/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for rullerzhou-afk/clawd-on-desk
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/rullerzhou-afk/clawd-on-desk)](https://getmerged.abhishekco.de/rullerzhou-afk/clawd-on-desk?utm_source=github&utm_medium=badge)

Active Good First Issues (0)

View on GitHub

No cached good first issues currently tracked for rullerzhou-afk/clawd-on-desk.

View all good first issues directly on GitHub

Looking for more JavaScript beginner tasks?Explore JavaScript GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for rullerzhou-afk/clawd-on-desk

When evaluating whether to contribute to rullerzhou-afk/clawd-on-desk, 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 rullerzhou-afk/clawd-on-desk acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 77.4% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to rullerzhou-afk/clawd-on-desk

01

Is rullerzhou-afk/clawd-on-desk welcoming to first-time open-source contributors?

rullerzhou-afk/clawd-on-desk has a recorded first-timer success rate of 57.1%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~2 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 53.6 C-Rank™ score represent?

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 53.6 places rullerzhou-afk/clawd-on-desk in the Solid tier.

04

What is the external contributor pull request merge rate for rullerzhou-afk/clawd-on-desk?

The external pull request merge rate is 77.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in rullerzhou-afk/clawd-on-desk?

rullerzhou-afk/clawd-on-desk does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for rullerzhou-afk/clawd-on-desk 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.