OmO: Just type "mass ulw" keyword with your prompt. Now you are the master of graph engineering.
C-Rank Grade: A (Welcoming) - 68/100
External PR Merge Rate: 56%
Response Time: 16h
First Timer Success: 26%
code-yeongyu/oh-my-openagent has a recorded first-timer success rate of 25.8%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in code-yeongyu/oh-my-openagent respond to incoming external pull requests in approximately 16.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 67.8 places code-yeongyu/oh-my-openagent in the A tier.
The external contributor pull request merge rate for code-yeongyu/oh-my-openagent is 56.2%, based on public PR activity from non-core contributors.
code-yeongyu/oh-my-openagent currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
OmO: Just type "mass ulw" keyword with your prompt. Now you are the master of graph engineering.
Highly welcoming maintainers in code-yeongyu/oh-my-openagent. Prompt code reviews with positive guidance for new contributors.
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/code-yeongyu/oh-my-openagent?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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~11 hours (70% approval). Large PRs (>500 lines) take ~78 hours (25% approval). Keep your diff compact for rapid review.
Prerequisites I will write this issue in English (see our Language Policy) I have searched existing issues and discussions to avoid duplicates This feature request is specific to oh-my-opencode (not OpenCode core) I have read the documentation or asked an AI coding agent with this project's GitHub URL loaded and couldn't find the answer Problem Description Momus reviews are expensive (1-2 min on gpt-5.4 xhigh, 32k thinking budget) but ephemeral. Once the session ends, the verdict is gone — no record of what was checked, what was flagged, or how many cycles a plan went through before approval. This means no audit trail when approved plans fail during execution, no revision history for debugging multi-cycle review loops, and wasted cost when sessions compact and Momus re-reviews from scratch. Proposed Solution Write verdicts alongside plans. Momus stays read-only — the orchestrator writes the artifact after receiving the result. .sisyphus/plans/ implement-auth.md implem
Prerequisites I will write this issue in English (see our Language Policy) I have searched existing issues and discussions to avoid duplicates This feature request is specific to oh-my-opencode (not OpenCode core) I have read the documentation or asked an AI coding agent with this project's GitHub URL loaded and couldn't find the answer Problem Description Summary Add Volcano Engine's Web Search API (Volcano Ark) as a third provider option alongside Exa and Tavily. Motivation Now that websearch is configurable between Exa and Tavily (#1371), it would be natural to extend the provider list further. Volcano Engine is ByteDance's enterprise AI cloud platform and offers a dedicated Web Search API through Volcano Ark that is well-suited for agent use cases — including structured results, citations, and coverage of real-time data categories like weather, flights, and local services. Implementation notes Volcano Ark's API uses an OpenAI-compatible format, so the adapter should slot i
Prerequisites I will write this issue in English (see our Language Policy) I have searched existing issues and discussions to avoid duplicates This feature request is specific to oh-my-opencode (not OpenCode core) I have read the documentation or asked an AI coding agent with this project's GitHub URL loaded and couldn't find the answer Problem Description Currently, to use the same model across all agents, users must manually configure each agent to point to the same category or model. This is verbose and requires updating every agent individually when the model changes. Proposed Solution Add a config option to make all agents automatically inherit Sisyphus's model. For example: { "agents": { "inherit_from_sisyphus": true } } Or a more flexible approach: { "agents": { "default_inherit": "sisyphus" } ### Alternatives Considered Using a shared category and pointing each agent to it manually — but this requires listing every agent and doesn't automatically updat
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 code-yeongyu/oh-my-openagent, 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 code-yeongyu/oh-my-openagent acknowledge new external contributions in approximately 16 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 56.2% were successfully merged into the primary branch.
code-yeongyu/oh-my-openagent has a recorded first-timer success rate of 25.8%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~16 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 67.8 places code-yeongyu/oh-my-openagent in the Welcoming tier.
The external pull request merge rate is 56.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, code-yeongyu/oh-my-openagent currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for code-yeongyu/oh-my-openagent 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.