Turn AI conversations into organized, reusable workflows — across major AI platforms. | 把 AI 对话转化为可组织、可复用的工作流，适用于主流 AI 平台
C-Rank Grade: A (Welcoming) - 61/100
External PR Merge Rate: 88%
Response Time: -
First Timer Success: 50%
urzeye/ophel has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in urzeye/ophel respond to incoming external pull requests in approximately 0.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 61.3 places urzeye/ophel in the A tier.
The external contributor pull request merge rate for urzeye/ophel is 87.8%, based on public PR activity from non-core contributors.
urzeye/ophel does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Turn AI conversations into organized, reusable workflows — across major AI platforms. | 把 AI 对话转化为可组织、可复用的工作流，适用于主流 AI 平台
Highly welcoming maintainers in urzeye/ophel. 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/urzeye/ophel?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 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 03:00 to 07:00 UTC (03:00 - 07:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (40% approval). Keep your diff compact for rapid review.
中文 ChatGPT 最近每天都在偷偷改页面结构，Ophel 的适配和发版节奏已经跟不上它改 DOM 的速度。我恨它！ 这不是单个偶发 bug，而是一个持续维护风险：ChatGPT 的页面结构、属性、虚拟滚动和原生 TOC 行为频繁变化，导致我们刚适配完、刚发版，几天后又失效。 这次的具体例子：原生 TOC / 用户问题大纲 在 1.0.57 附近，我们已经适配过 ChatGPT 页面原生 TOC，用它作为大纲里的用户问题来源。旧逻辑假设 TOC rail 里有 Prompt N 按钮，并且问题文本可以从已挂载的 TOC 标题节点中读取。 但最近 ChatGPT 又改了： TOC 未悬浮时，button 的 aria-label 是 Prompt 1、Prompt 2 这种占位文本。 TOC 悬浮后，同一批 button 的 aria-label 才会被动态替换成真实用户问题。 如果不触发 hover，就读不到完整问题文本。 如果回退到当前 DOM 消息节点，由于 ChatGPT 长会话虚拟滚动，只能拿到当前
Hello community! 👋 We've been working hard to make Ophel the best AI assistant for Gemini, ChatGPT, Claude, and more. We believe Ophel can significantly improve people's productivity and reading experience. However, building a great tool is only half the battle. We need YOUR help to let the world know about it! 🌍 How you can help: Share on Social Media: Tweet about Ophel on X (Twitter), share it on Reddit (e.g., r/ChromeExtensions, r/ArtificialInteligence, r/OpenAI), or post on Hacker News. Product Hunt: If you haven't already, please support our upcoming launch on Product Hunt! (Link TBD) Blog & Video: Write a blog post or make a short video review on YouTube/TikTok. Connect with Influencers: If you know any tech KOLs, YouTubers, or bloggers (especially in the English-speaking world) who review AI tools or browser extensions, please recommend Ophel to them! Mentioning them in this thread or tagging them on social media would be amazing. If you have shared Ophel somewhere, plea
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 urzeye/ophel, 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 urzeye/ophel acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 87.8% were successfully merged into the primary branch.
urzeye/ophel has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 61.3 places urzeye/ophel in the Welcoming tier.
The external pull request merge rate is 87.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
urzeye/ophel does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for urzeye/ophel 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.