Comet: agent skill harness for turning ideas into evaluated workflows
C-Rank Grade: A (Welcoming) - 69/100
External PR Merge Rate: 77%
Response Time: 22h
First Timer Success: 82%
rpamis/comet has a recorded first-timer success rate of 81.8%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in rpamis/comet respond to incoming external pull requests in approximately 21.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 68.5 places rpamis/comet in the A tier.
The external contributor pull request merge rate for rpamis/comet is 76.5%, based on public PR activity from non-core contributors.
rpamis/comet currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Comet: agent skill harness for turning ideas into evaluated workflows
Collaborative maintainer environment in rpamis/comet. 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/rpamis/comet?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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~14 hours (96% approval). Large PRs (>500 lines) take ~104 hours (34% approval). Keep your diff compact for rapid review.
🔎 Existing issue check 已搜索现有 issue。相关：#352（要求区分 CodeGraph CLI／项目索引／MCP 注册三态）、#409（doctor 漏检 Codex 项目级 CodeGraph MCP 配置并误报未注册，已闭）、#135（doctor 其它假阴性，已在 0.4.0-beta.1 修复）。 上述均未覆盖本报告的两个问题：parseJsonLike() 的块注释剥离不识别字符串字面量，以及 inspectJsonMcpEntry() 不识别 opencode v2 的 mcp.servers.<name> 形状。 🎯 Affected area domains/integrations/codegraph.ts（parseJsonLike / inspectJsonMcpEntry），以及 comet doctor 的 CodeGraph 注册诊断输出。 📦 Comet version 0.4.4（npm latest，即当前无更新版本可等）。宿主：opencode v2.0.26，Linux/WSL2。 💥 Current behavior comet doctor --json 对 opencode 报： { "id": "opencode", "scope": "both", "configPath": "~/.config/opencode/opencode.jsonc", "registered": false, "valid": false, "effective": false, "detail": "unable to read ~/.confi
🧭 Problem Comet 目前没有 Prime Agent（PrimeIntellect-ai/prime-agent）平台适配，在 Prime Agent 项目里无法原生安装 Comet 工作流。 dist/platform/install/platforms.js 的 PLATFORMS 里有 30+ 个平台（含 pi、oh-my-pi、dsh 等），但没有 prime-agent。我实测了在当前项目里直接跑 comet init --platform prime-agent（Comet CLI 0.4.3，Prime Agent 0.9.8），结果分三部分： 1. Skills 装到了 Prime Agent 读不到的位置 CLI 没有校验 platform id 是否在 PLATFORMS 里，而是从 id 推导目录名，生成了： .prime-agent/skills/comet/SKILL.md .prime-agent/skills/comet-native/SKILL.md .prime-agent/rules/comet-workflow-guard.md .prime-agent/settings.local.json # 含 PreToolUse hook 但 Prime Agent 的 skill 发现路径是（docs/skills.md）： 全局：~/.prime/agent/skills/、~/.agents/skills/ 项目：.prime/agent/skills/、以及 cwd 到 git 根之间各级的 .agents/skills/ 另有 packages / settings / --skill / 内
🔎 Existing issue check I have searched the existing issues. 🎯 Affected area Dashboard (domains/dashboard) 📦 Comet version 0.4.3 💥 Current behavior 记录了项目记忆条数过多时，dashboard无法滚动查看 ✅ Expected behavior 能够滚动查看项目记忆，复用现有的dashboard内页滚动效果，参考检索测试 🔁 Steps to reproduce 1 🖥️ Environment - OS: - Shell: - Node: - Package manager: - Install scope: project / global - Skill language: en / zh - Target AI platform(s): 📋 Logs or output 🧩 Additional context No response
🔎 Existing issue check I have searched the existing issues. 🧭 Problem 现在只能够通过cc和codex环境兼容dsh、comet未原生支持dsh init ✨ Proposed solution 期望 原生在comet init、comet update、comet uninstall中支持dsh 包括skill、rule、hook、script、reference分发 复用现在comet cli中既有逻辑，需调查dsh官方各种功能安装路径 🎯 Primary area Platform adapter / installer (platform/*) 🪐 Workflow phase None 🔀 Alternatives considered No response 🧰 Compatibility notes No response 🧩 Additional context No response
🔎 Existing issue check Searched open and closed issues for workspace, classicCommandProjectRoot, and context unavailable. No duplicate found (#302 is the feature that introduced the command; #304 is a different CWD-resolution bug in guard). 🎯 Affected area Classic workflow runtime (domains/comet-classic) 📦 Comet version 0.4.0-beta.18 (latest published) 💥 Current behavior Every comet classic workspace invocation fails with exit code 70 and Classic command project context is unavailable. This affects both subcommands (prepare, resolve) and all three isolation modes (current, branch, worktree) — six combinations, same error. Because comet-open step 0b instructs the agent to run comet classic workspace prepare <name> --isolation <mode> before creating OpenSpec artifacts and .comet.yaml, the documented Classic open flow cannot complete as written. In practice current isolation is unaffected in outcome (prepare creates no branch or directory, and comet state init --isolation cu
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 rpamis/comet, 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 rpamis/comet acknowledge new external contributions in approximately 21 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 76.5% were successfully merged into the primary branch.
rpamis/comet has a recorded first-timer success rate of 81.8%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~21 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 68.5 places rpamis/comet in the Welcoming tier.
The external pull request merge rate is 76.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, rpamis/comet 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 rpamis/comet 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.