Organization-as-Code for autonomous AI agents. Brain-inspired memory that grows, consolidates, and forgets. Multi-model (Claude/Codex/Gemini/Cursor/Ollama).
C-Rank Grade: B (Solid) - 53/100
External PR Merge Rate: 69%
Response Time: -
First Timer Success: 60%
xuiltul/animaworks has a recorded first-timer success rate of 60.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in xuiltul/animaworks 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 52.6 places xuiltul/animaworks in the B tier.
The external contributor pull request merge rate for xuiltul/animaworks is 68.9%, based on public PR activity from non-core contributors.
xuiltul/animaworks currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in xuiltul/animaworks. Maintains strict focus on technical quality and test standards.
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/xuiltul/animaworks?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (86% approval). Large PRs (>500 lines) take ~115 hours (31% approval). Keep your diff compact for rapid review.
Summary Improve accessibility by adding aria-label and aria-describedby attributes to interactive elements in the web UI. What to do Audit server/static/ for buttons, inputs, and controls that lack accessibility attributes. Priority areas: Theme selector cards Chat input and send button Voice chat controls (mic, stop) Settings page toggles and sliders Navigation links and sidebar items Modal close buttons How to verify Use browser DevTools Accessibility panel to check for missing labels Run Lighthouse accessibility audit Test with a screen reader if possible Notes Use descriptive labels (e.g. aria-label="Send message" not aria-label="Button") Localized strings can use the i18n system if applicable, but English-only is fine as a first pass
Summary Add a Simplified Chinese locale to the template system. AnimaWorks uses locale-based template directories (templates/ja/, templates/en/) for prompts, common knowledge, skills, and Anima scaffolding. What to do Create templates/zh/ mirroring the structure of templates/en/ Translate all Markdown files from English into Simplified Chinese Scope ~150 files across these categories: Directory Content prompts/ System prompt fragments (builder, environment, behavior rules) common_knowledge/ Shared knowledge docs (organization, operations, security, troubleshooting) common_skills/ Skill definitions (tool usage guides) anima_templates/ Anima scaffolding (identity, injection, permissions, heartbeat) roles/ Role-specific templates (engineer, manager, writer, etc.) bootstrap.md First-run instructions Reference templates/en/ — English (source of truth) templates/ja/ — Japanese (for reference) Notes This is a large task — partial PRs are welcome (e.g. just commo
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 xuiltul/animaworks, 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 xuiltul/animaworks acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 68.9% were successfully merged into the primary branch.
xuiltul/animaworks has a recorded first-timer success rate of 60.0%. Repositories ranked Solid 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 52.6 places xuiltul/animaworks in the Solid tier.
The external pull request merge rate is 68.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, xuiltul/animaworks 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 xuiltul/animaworks 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.