The collaboration layer for AI teams: domain experts annotate and review agent behavior, engineers improve the agent from what they find.
C-Rank Grade: S (Elite) - 78/100
External PR Merge Rate: 93%
Response Time: 4d
First Timer Success: 91%
rhesis-ai/rhesis has a recorded first-timer success rate of 90.9%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in rhesis-ai/rhesis respond to incoming external pull requests in approximately 97.4 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 78.1 places rhesis-ai/rhesis in the S tier.
The external contributor pull request merge rate for rhesis-ai/rhesis is 93.0%, based on public PR activity from non-core contributors.
rhesis-ai/rhesis currently has 6 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in rhesis-ai/rhesis. 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/rhesis-ai/rhesis?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Summary Enable Confluence as an MCP-backed extract provider so users can import pages and documentation from Confluence spaces into Rhesis for test generation and Architect grounding. Problem / Opportunity Confluence is already a supported ToolProviderType with REST test-connection, and an SDK provider template exists (confluence.json.j2 via mcp-atlassian). However, Confluence is not wired for MCP extract today — users cannot import Confluence content into Knowledge the way they can from Notion, GitHub, or Linear. Proposal Extend the existing Confluence provider to support MCP extract (similar to how other providers route extract through MCP): Backend Route confluence extract + test-connection through MCP in services/tool/actions.py (keep or migrate existing REST test-connection as needed) Add/extend provider-specific credential validation in routers/tools.py credentials: CONFLUENCE_URL, CONFLUENCE_USERNAME, CONFLUENCE_API_TOKEN tool_metadata: optional scope such as { "space_key":
Summary Add monday.com as a supported MCP tool provider so users can import boards, items, and project context from monday.com into Rhesis for test generation and Architect grounding. Problem / Opportunity monday.com is a widely used work-management platform for roadmaps, requirements, and delivery tracking. Teams storing specs and work items on monday boards currently have no way to connect them to Rhesis. Proposal Follow the established provider pattern (GitLab, Asana, Shortcut, Linear, Azure DevOps): Backend Add monday ToolProviderType to a new Alembic migration (chain from current head; add merge migration if needed) Route monday extract + test-connection through MCP in services/tool/actions.py Add provider-specific credential/metadata validation in routers/tools.py credentials: MONDAY_TOKEN (monday.com personal API token) tool_metadata: optional scope such as { "board_id": "..." } if supported by the MCP server SDK Add sdk/src/rhesis/sdk/agents/mcp/provider_templates/monday.
Summary Add ClickUp as a supported MCP tool provider so users can import tasks, docs, and project context from ClickUp into Rhesis for test generation and Architect grounding. Problem / Opportunity ClickUp is widely used for project management, requirements tracking, and team docs. Users storing specs and tasks in ClickUp currently have no way to connect it to Rhesis — they must copy-paste content manually. Proposal Follow the established provider pattern (GitLab, Asana, Shortcut, Linear, Azure DevOps): Backend Add clickup ToolProviderType to a new Alembic migration (chain from current head; add merge migration if needed) Route clickup extract + test-connection through MCP in services/tool/actions.py Add provider-specific credential/metadata validation in routers/tools.py Evaluate auth options during implementation: Preferred for headless Rhesis: community/API-token MCP server if stable Official: ClickUp hosted MCP at https://mcp.clickup.com/mcp (OAuth-only — may need token stor
Summary Add Trello as a supported MCP tool provider so users can import boards, cards, and project context from Trello into Rhesis for test generation and Architect grounding. Problem / Opportunity Trello remains a common lightweight project-management tool, especially for smaller teams and Kanban workflows. Users tracking requirements on Trello boards have no way to connect them to Rhesis today. Proposal Follow the established provider pattern (GitLab, Asana, Shortcut, Linear, Azure DevOps): Backend Add trello ToolProviderType to a new Alembic migration (chain from current head; add merge migration if needed) Route trello extract + test-connection through MCP in services/tool/actions.py Add provider-specific credential/metadata validation in routers/tools.py credentials: TRELLO_API_KEY, TRELLO_TOKEN tool_metadata: optional scope such as { "board_id": "..." } (same pattern as Asana workspace_gid / Linear team_id) SDK Add sdk/src/rhesis/sdk/agents/mcp/provider_templates/trello.jso
Summary Add full OpenAI SDK integration: automatic telemetry instrumentation of openai client calls and a OpenAITarget for Penelope conversation testing. Problem / Opportunity Users calling the OpenAI API directly (not via LangChain/LangGraph) have no automatic observability and cannot use Penelope to test their AI applications without manual wiring. Related manual instrumentation examples: #1832, #1856 Part of container issue: #1083 Proposal Auto-instrumentation Implement OpenAIIntegration in sdk/src/rhesis/sdk/telemetry/integrations/openai.py by monkey-patching or wrapping openai.ChatCompletion / openai.chat.completions.create to automatically capture: Input/output messages Token usage (prompt, completion, total) Model name and provider detection Latency and errors Register in sdk/src/rhesis/sdk/telemetry/integrations/__init__.py. Penelope Target Implement OpenAITarget in penelope/src/rhesis/penelope/targets/openai.py wrapping the openai client so Penelope can run multi-turn conver
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 rhesis-ai/rhesis, 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 rhesis-ai/rhesis acknowledge new external contributions in approximately 4 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 93.0% were successfully merged into the primary branch.
rhesis-ai/rhesis has a recorded first-timer success rate of 90.9%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~4 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 78.1 places rhesis-ai/rhesis in the Elite tier.
The external pull request merge rate is 93.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, rhesis-ai/rhesis currently has 6 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for rhesis-ai/rhesis 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.