x-cli examples
C-Rank Grade: B (Solid) - 48/100
External PR Merge Rate: 70%
Response Time: 18h
First Timer Success: 50%
better-world-ai/x-cli has a recorded first-timer success rate of 50.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in better-world-ai/x-cli respond to incoming external pull requests in approximately 18.2 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 47.8 places better-world-ai/x-cli in the B tier.
The external contributor pull request merge rate for better-world-ai/x-cli is 70.0%, based on public PR activity from non-core contributors.
better-world-ai/x-cli currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in better-world-ai/x-cli. Reviews community pull requests with focus on project quality.
Discussions in better-world-ai/x-cli 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/better-world-ai/x-cli?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~12 hours (88% approval). Large PRs (>500 lines) take ~87 hours (32% approval). Keep your diff compact for rapid review.
Review #62 的时候发现的。 现象 search-en 的输出结构会因为加不加 --workspace 而改变，而且和三个浏览器命令不一致： 调用 输出 search-en --query X {papers, total, sources} search-en --query X --workspace D {search: {papers, total, sources}, workspace, papers_added, total_stored} ← 多包了一层 search-google --query X --workspace D {papers, total, source, workspace, papers_added, total_stored} ← 平铺 根源是 scholar-cli/cmd/root.go:123 这一行： output.Success(map[string]any{ "search": result, // ← 把整个 result 塞进一个 key，多了一层嵌套 "workspace": workspace, "papers_added": added, "total_stored": s.Count(), }) 而 #63 之后三个浏览器命令走的是 emitSearch（root.go:56），它是平铺的： output.Success(map[string]any{ "papers": papers, "total": len(papers), "source": source, "workspace": workspace, "papers_added": add
背景 #50 重排 README 时发现，boss-cli 是仓库里唯一既没有 recipe、也没有配套 skill 的 CLI： 场景 用到的 CLI 完整脚本 找工作 boss-cli 暂无 ← 对比其他场景——租房有 rental-assistant，行程有 travel-planning，高考有 gaokao-assistant，文献有 paper-research——boss-cli 是个裸 CLI，agent 拿到它不知道该怎么编排。 问题一：参数是裸数字码，没有文档 boss-cli search-jobs --query "前端开发" --city 101020100 --salary 404 --experience 105 101020100、404、105 分别是什么，boss-cli/README.md 里没有对照表。用户不可能猜出来，agent 也不能。 对比 58-cli/README.md 的做法——它在 README 末尾列了城市码对照： sz=深圳, sh=上海, bj=北京, gz=广州, ... boss-cli 应该照这个补上城市码、薪资档位、经验档位三张对照表。这是最小、也最该先做的一件事。 问题二：没有配套 skill 找工作跟租房是同构的任务
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 better-world-ai/x-cli, 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 better-world-ai/x-cli acknowledge new external contributions in approximately 18 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 70.0% were successfully merged into the primary branch.
better-world-ai/x-cli has a recorded first-timer success rate of 50.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~18 hours. 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 47.8 places better-world-ai/x-cli in the Solid tier.
The external pull request merge rate is 70.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, better-world-ai/x-cli currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for better-world-ai/x-cli 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.