Supercharge Claude Code with 11 AI agents, 36 commands & 15 skills — the claude-code plugin framework inspired by oh-my-zsh. 6-layer security hooks included. 5-min install.
C-Rank Grade: B (Solid) - 70/100
External PR Merge Rate: 88%
Response Time: <1h
First Timer Success: 100%
sangrokjung/claude-forge 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 sangrokjung/claude-forge respond to incoming external pull requests in approximately 0.9 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 70.2 places sangrokjung/claude-forge in the B tier.
The external contributor pull request merge rate for sangrokjung/claude-forge is 87.5%, based on public PR activity from non-core contributors.
sangrokjung/claude-forge currently has 12 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in sangrokjung/claude-forge welcoming community pull requests and bug fixes.
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/sangrokjung/claude-forge?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 17:00 UTC (17:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~4 hours (39% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Shell.
Repository for all things Node-RED and Docker related
Actively maintained binary package repo for Arch Linux of free and open source pro-audio software.
Provides network connectivity to WSL 2 when blocked by VPN
Two LOW findings from the v4.0 final re-review — neither introduced by the release's fixes, neither blocking, both worth a small pass. Lifecycle event-count arithmetic doesn't reconcile. README.md:351 and README.ko.md:269 assert 21-event coverage, but the tree yields: settings.json wires 8 distinct events, hooks/examples/ covers 9 (2 overlapping) = 15 distinct; hooks/README.md's own catalog lists 22 events (16 with a shipped handler) and claims 27 total while 22 + 6 spec-only = 28. Reconcile hooks/README.md's catalog first, then re-derive the three READMEs' counts from that single source. scripts/tests/test_s5_hooks.sh leaves artifacts. No cleanup trap: its mktemp WORK dir and the run's /tmp/claude-loop-detect-* and /tmp/auto-verify-fix-* state files survive every invocation, and CI now runs the suite on every push. Suggested fix: add an EXIT trap that removes the WORK directory and the RUN_ID-scoped /tmp state files. 🤖 Generated with Claude Code
Deferred from the v4.0 survey (theme C). A review lens orthogonal to code-review: did we build MORE than asked, is complexity proportionate, did scope drift mid-task. Cheap to port, pairs well with the adversarial loop. Survey rationale archive: the maintainer's internal survey report (2026-08-18) ranked and scoped all deferred sets; ask in comments if you want the full rationale for this one. 🤖 Generated with Claude Code
Deferred from the v4.0 survey (theme C). Lock a definition-of-done before implementation starts; verify-agent then judges each DoD item PASS/FAIL/MANUAL at the end. Fills the gap between /plan and /verify-loop. Survey rationale archive: the maintainer's internal survey report (2026-08-18) ranked and scoped all deferred sets; ask in comments if you want the full rationale for this one. 🤖 Generated with Claude Code
Deferred from the v4.0 survey (theme D, effort S). A stdlib-only helper that renders any outward mutation (send, publish, bid, env change) as a secret-masked request shape for review before firing. Pattern + ~80-line script. Survey rationale archive: the maintainer's internal survey report (2026-08-18) ranked and scoped all deferred sets; ask in comments if you want the full rationale for this one. 🤖 Generated with Claude Code
Deferred from the v4.0 survey (theme G, all effort S). pull-main: conflict-safe main→dev merge with auto-backup branch and rollback matrix. worktree-collision-detect: SessionStart warning when two sessions share one working tree. push-before-ci: run CI-identical commands locally before push (includes the bracket-glob false-pass trap writeup). Survey rationale archive: the maintainer's internal survey report (2026-08-18) ranked and scoped all deferred sets; ask in comments if you want the full rationale for this one. 🤖 Generated with Claude Code
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 sangrokjung/claude-forge, 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 sangrokjung/claude-forge acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 87.5% were successfully merged into the primary branch.
sangrokjung/claude-forge 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 ~<1 hour. 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 70.2 places sangrokjung/claude-forge in the Solid tier.
The external pull request merge rate is 87.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, sangrokjung/claude-forge currently has 12 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for sangrokjung/claude-forge 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.