Claude Code plugin for Elixir/Phoenix/LiveView — 26 specialist agents, Iron Laws enforcement, and Tidewave MCP integration. Plan features with parallel research agents, execute with automatic verification, review with 4-agent parallel audits, and capture learnings as reusable knowledge.
C-Rank Grade: B (Solid) - 49/100
External PR Merge Rate: 60%
Response Time: 8d
First Timer Success: 100%
oliver-kriska/claude-elixir-phoenix has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in oliver-kriska/claude-elixir-phoenix respond to incoming external pull requests in approximately 187.8 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 48.8 places oliver-kriska/claude-elixir-phoenix in the B tier.
The external contributor pull request merge rate for oliver-kriska/claude-elixir-phoenix is 60.0%, based on public PR activity from non-core contributors.
oliver-kriska/claude-elixir-phoenix currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Claude Code plugin for Elixir/Phoenix/LiveView — 26 specialist agents, Iron Laws enforcement, and Tidewave MCP integration. Plan features with parallel research agents, execute with automatic verification, review with 4-agent parallel audits, and capture learnings as reusable knowledge.
Collaborative maintainer environment in oliver-kriska/claude-elixir-phoenix. Reviews community pull requests with focus on project quality.
Discussions in oliver-kriska/claude-elixir-phoenix 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/oliver-kriska/claude-elixir-phoenix?utm_source=github&utm_medium=badge)
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 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~122 hours (75% approval). Large PRs (>500 lines) take ~901 hours (27% approval). Keep your diff compact for rapid review.
Background From the closed #48 Tier 1 plan. We have skill-effectiveness telemetry (metrics.jsonl, currently 257 rows; populated by skill-monitor), but no lifecycle layer on top of it. Skills accumulate forever — drift, listing-budget pressure, listing-routing degradation as the catalog grows. Port the pure-function approach from hermes-agent's apply_automatic_transitions (agent/curator.py:200-260 in their repo): walk telemetry, mark transitions, never auto-delete. Zero LLM cost. Concrete tasks New lab/eval/skill_lifecycle.py (~120 lines, pure Python) Walk metrics.jsonl and compute per-skill last_triggered_at, trigger_count, last_failed_route_at Apply transitions: active → stale when zero triggers in last N=20 eval runs AND zero ccrider invocations in last 30 days stale → review_candidate after 90 days NEVER auto-delete — write to .claude/skill-lifecycle.md for human triage Add pinned: true field to Iron Law / intro / help skills in their frontmatter (lifecycle skips the
Background Phase 1 of T1.3 shipped in v2.10.3 (commit 3ea7298): lab/eval/trigger_scorer.py --model <id> works against any Anthropic model, with per-model cache layout under lab/eval/triggers/results/by-model/{model}/ and the N-way comparator lab/eval/compare_models.py. What's still missing: support for non-Claude routing judges (gpt-4o-mini for Codex, qwen/etc. for OpenCode and Pi). This gates the claim in PR #46 that the plugin "works on Codex/OpenCode/Pi" — today our descriptions are tuned only against claude-haiku-4-5, and we have zero data on how they trigger on other model families. Original analysis: see closed #48 (umbrella) and the local research doc .claude/research/2026-05-09-hermes-waza-improvement-plan.md (T1.3). Why this is urgent v3.0.0 multi-agent port (PR #46) is sitting on a routing-verification gap. Phase 1 already showed that even within Anthropic, sonnet routes some skills 8–12 pts better than haiku on the same descriptions; we have no idea whether gpt-4o-mini i
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 oliver-kriska/claude-elixir-phoenix, 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 oliver-kriska/claude-elixir-phoenix acknowledge new external contributions in approximately 7 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 60.0% were successfully merged into the primary branch.
oliver-kriska/claude-elixir-phoenix has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~7 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 48.8 places oliver-kriska/claude-elixir-phoenix in the Solid tier.
The external pull request merge rate is 60.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, oliver-kriska/claude-elixir-phoenix 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 oliver-kriska/claude-elixir-phoenix 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.