通用女仆机器人本地版 Rust 服务
C-Rank Grade: A (Welcoming) - 69/100
External PR Merge Rate: 96%
Response Time: 2d
First Timer Success: 75%
kuliantnt/qq-maid-bot has a recorded first-timer success rate of 75.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kuliantnt/qq-maid-bot respond to incoming external pull requests in approximately 47.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 69.2 places kuliantnt/qq-maid-bot in the A tier.
The external contributor pull request merge rate for kuliantnt/qq-maid-bot is 96.2%, based on public PR activity from non-core contributors.
kuliantnt/qq-maid-bot currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in kuliantnt/qq-maid-bot. 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/kuliantnt/qq-maid-bot?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~31 hours (96% approval). Large PRs (>500 lines) take ~225 hours (43% approval). Keep your diff compact for rapid review.
背景 当前部分功能可能需要较长时间才能完成，例如 /查 联网查询。 任务执行期间，用户可能出现以下需求： 查询方向已经不再需要，希望立即停止； 同时发起了多个耗时请求，希望查看它们是否仍在运行； 已经发送停止命令，但旧请求仍继续产生或发送输出； 后续接入 Codex、文件处理或 Agent 能力时，需要复用同一套任务管理方式。 如果每个功能分别实现自己的运行状态、取消逻辑和输出控制，后续会形成多套互不兼容的流程。 因此，希望增加一层统一的 Tasks Flow，用于描述和管理耗时任务的创建、运行、完成、失败与停止。 首个接入 Tasks Flow 的能力为 /查。 用户故事 用户故事 1：耗时查询被识别为任务 作为用户，当我发送： /查 Rust 最近版本有什么变化 机器人可以将本次查询识别为一个独立任务，并在适当时展示： 任务 #1 正在查询：
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 kuliantnt/qq-maid-bot, 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 kuliantnt/qq-maid-bot acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 96.2% were successfully merged into the primary branch.
kuliantnt/qq-maid-bot has a recorded first-timer success rate of 75.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 69.2 places kuliantnt/qq-maid-bot in the Welcoming tier.
The external pull request merge rate is 96.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, kuliantnt/qq-maid-bot 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 kuliantnt/qq-maid-bot 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.