Claude Code. Any Model. The most powerful AI coding agent now speaks every language.
C-Rank Grade: B (Solid) - 49/100
External PR Merge Rate: 44%
Response Time: 3h
First Timer Success: 20%
MadAppGang/claudish has a recorded first-timer success rate of 20.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in MadAppGang/claudish respond to incoming external pull requests in approximately 3.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 49.3 places MadAppGang/claudish in the B tier.
The external contributor pull request merge rate for MadAppGang/claudish is 43.7%, based on public PR activity from non-core contributors.
MadAppGang/claudish does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Claude Code. Any Model. The most powerful AI coding agent now speaks every language.
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/MadAppGang/claudish?utm_source=github&utm_medium=badge)
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
claudish --free [1] 84928 killed claudish --free MacOS via brew tap MadAppGang/tap && brew install claudish
Summary This feature introduces KeyPool, a transparent multi-key rotation and failover system for all API providers. Users can supply multiple API keys per provider via comma-separated environment variables, and Claudish will automatically distribute requests across keys with intelligent failover on errors. # Before: single key, single point of failure export GEMINI_API_KEY="key1" # After: multiple keys, automatic rotation on errors export GEMINI_API_KEY="key1,key2,key3" No CLI changes, no configuration flags — just add more keys to the same environment variable. Motivation API rate limits (HTTP 429) are a common friction point when using LLM providers heavily. When a key is rate-limited, the user must wait or manually switch keys. Similarly, expired or revoked keys cause hard failures with no recovery path. Multi-key rotation addresses this: Rate limit resilience: When one key hits 429, the next key is tried immediately Key lifecycle management: Expired or invalid keys are skipped
Summary Add support for AWS Bedrock as a provider using a BYOK (Bring Your Own Key) approach, with a model selection option. Motivation Many users already have access to foundation models through AWS Bedrock. Supporting Bedrock would allow them to use their existing AWS credentials instead of managing separate API keys for each model provider. This would be especially useful for: Users running infrastructure on AWS Enterprise environments with IAM-based authentication Accessing multiple models (Claude, Llama, Mistral, etc.) through a single provider Proposed Behavior User adds AWS credentials (BYOK) for Bedrock. Claudish detects available Bedrock models. User can select the model to use. Example usage: claudish --provider bedrock --model anthropic.claude-3-5-sonnet Or after configuration: claudish --model [email protected] Possible Features Support for AWS access key or IAM role Automatic listing of available Bedrock models Model selection during configuration Co
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 MadAppGang/claudish, 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 MadAppGang/claudish acknowledge new external contributions in approximately 3 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 43.7% were successfully merged into the primary branch.
MadAppGang/claudish has a recorded first-timer success rate of 20.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 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 49.3 places MadAppGang/claudish in the Solid tier.
The external pull request merge rate is 43.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
MadAppGang/claudish 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 MadAppGang/claudish 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.