RachelForster/Shinsekai - Open Source PR Review Scorecard

AI RPG maker

C-Rank Grade: S (Elite) - 72/100

External PR Merge Rate: 74%

Response Time: 12h

First Timer Success: 100%

Frequently Asked Questions

Is RachelForster/Shinsekai welcoming to first-time open-source contributors?

RachelForster/Shinsekai has a recorded first-timer success rate of 100.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in RachelForster/Shinsekai respond to incoming external pull requests in approximately 11.6 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 71.8 C-Rank™ score (S Tier) represent?

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 71.8 places RachelForster/Shinsekai in the S tier.

What is the external contributor pull request merge rate for RachelForster/Shinsekai?

The external contributor pull request merge rate for RachelForster/Shinsekai is 74.3%, based on public PR activity from non-core contributors.

Are there Good First Issues available in RachelForster/Shinsekai?

RachelForster/Shinsekai currently has 9 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

RachelForster
RachelForster/ShinsekaiS•Elite610
GitHub
Back to Explorer
RachelForster

RachelForster/Shinsekai

610
Active (30d)S•Elite(72/100)Python

AI RPG maker

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Maintainer

Warmth Score
7.8/10
Patience Score
8.2/10
Nitpick Rate
20%

Active maintainer team in RachelForster/Shinsekai welcoming community pull requests and bug fixes.

Top PR Submission Do's

  • •Ensure code complies with repository style conventions
  • •Keep PRs focused and well-documented

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without context
  • •Do not break existing automated test suites
Response Velocity
11 hours
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
74.3%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
100.0%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
4 core
Small core review team
Diagnostic Health HUD
74.3%
Merge Gauge
100.0%
1st-Timer
Community Vibe81/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for RachelForster/Shinsekai
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/RachelForster/Shinsekai)](https://getmerged.abhishekco.de/RachelForster/Shinsekai?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

摘要 / Summary Improve the discoverability of plugin developer documentation by adding more visible entry points in the repository, website, and possibly the application UI. 希望提升插件开发者文档的可见性,让新手和潜在插件作者更容易找到入口。 当前讨论中提到: 更新文档和网站; 仓库中的英文 Markdown 也需要同步更新; 将网站放到 README 中更显眼的位置; 也可以考虑在软件本体中加入入口,例如插件相关工具栏; 目前网站和开发者文档入口“藏得很深”,知道的人较少。 背景 / Background The plugin developer documentation appears to exist, but its entry points are not obvious enough for new contributors or plugin authors. 目前问题重点不是插件开发文档内容本身缺失,而是入口不够明显,导致想开发插件的人可能需要翻找仓库或依赖他人指引。 这会影响: 新插件作者了解插件开发流程; 新贡献者参与插件生

📅 Opened Jul 1, 2026💬 0 comments
Quality: 50/100Contribute

摘要 / Summary Add a built-in Shinsekai development skill to help contributors understand the project and use AI-assisted coding more effectively. 希望新增一个面向 contributor 的 Shinsekai dev skill,用于辅助贡献者进行开发、调试和 AI 辅助编码(vibe coding)。 该 Skill 的目标不是面向普通用户的使用教程,而是帮助潜在贡献者更快理解项目结构、开发流程、常见入口和贡献注意事项。 需求背景 / Background The request is to provide a contributor-facing skill focused on development guidance rather than user tutorials or content creation. 当前材料中的原始需求为: 写一个 Shinsekai dev skill,方便 contributor vibe coding 从语义上看,这更像是一个内置开发辅助 Skill / 贡献者指南模板。它可以帮助贡献者在使用 AI 助手参与项目开发时,更准确地理解仓库约束、模块边界和常见任务流程,减少盲目修改或误改关键路径的概率。 预

📅 Opened Jun 26, 2026💬 0 comments
Quality: 50/100Contribute

摘要 / Summary Move the in-window notification from the bottom-right corner to the top center to improve visibility and layout consistency. 希望将当前位于窗口右下角的 notification 提示移动到窗口上方居中显示。 该需求属于前端 UI / UX 调整,当前材料未说明这是现有异常或错误,因此按体验优化处理。 需求描述 / Request The requested change is a UI placement adjustment for the notification component. 当前说明:把右下角的 notification 移到窗口上方居中。 调整目标: notification 不再显示在窗口右下角; notification 显示在窗口顶部区域,并保持水平居中; 尽量保留原有 notification 的触发、更新、自动隐藏等行为。 预期行为 / Expected behavior Notifications should appear near the top center of the window and keep their existing display behavior. 触发 notification 时,提示应显示在窗口上方居中的位置。 建议表现: 横向相对于窗口居

📅 Opened Jun 24, 2026💬 0 comments
Quality: 40/100Contribute

现象 目前希望增加一种角色与界面互动能力:角色可以让 UI 中的按钮消失,并且最好是动态消失,而不是瞬间隐藏。 复现步骤 待补充:目前只有功能需求描述,尚未提供具体页面、按钮范围、触发方式或角色配置方式。 期望行为 希望支持角色触发 UI 按钮隐藏/显示,例如: 角色可以让指定 UI 按钮消失; 按钮消失时最好带有动态效果,例如淡出、缩放、位移等; 如可行,角色也应能让按钮重新显示; 默认状态下应保持现有 UI 按钮正常显示,不影响已有操作; 应考虑保留兜底恢复方式,避免关键按钮被隐藏后用户无法继续操作或恢复界面。 实际行为 当前未提供该能力的具体表现说明。根据需求描述,现有 UI 按钮暂不能由角色动态控制隐藏。 日志/截图 暂无。 相关但不完全重复的 issue #113:该 issue 关注人物立绘在情绪或状态变化时增加动态

📅 Opened Jun 17, 2026💬 0 comments
Quality: 30/100Contribute

现象 当前模板生成能力希望进一步增强:在生成模板时加入“随机情景”和“人物之间的复杂关系”,以提升生成内容的多样性和可玩性。 复现步骤 暂无明确复现步骤。该需求更偏向功能增强。 期望行为 模板生成时可以自动引入随机情景。 模板生成时可以包含人物之间更复杂的关系设定。 生成结果应能体现情景变化与人物关系带来的差异。 实际行为 当前材料中未提供现有模板生成的具体表现,暂无法确认当前是否完全缺失该能力,或只是随机性/复杂度不足。 日志/截图 暂无日志或截图。 待补充信息 当前模板生成入口或功能位置。 现有模板生成示例。 希望支持的随机情景类型示例。 希望支持的人物复杂关系示例。 是否需要配置开关、强度参数或可编辑关系模板。 相关版本信息。 Labels labels: feature request llm p2

📅 Opened Jun 16, 2026💬 0 comments
Quality: 15/100Contribute
Looking for more Python beginner tasks?Explore Python GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for RachelForster/Shinsekai

When evaluating whether to contribute to RachelForster/Shinsekai, 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 RachelForster/Shinsekai acknowledge new external contributions in approximately 11 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 74.3% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to RachelForster/Shinsekai

01

Is RachelForster/Shinsekai welcoming to first-time open-source contributors?

RachelForster/Shinsekai has a recorded first-timer success rate of 100.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~11 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 71.8 C-Rank™ score represent?

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 71.8 places RachelForster/Shinsekai in the Elite tier.

04

What is the external contributor pull request merge rate for RachelForster/Shinsekai?

The external pull request merge rate is 74.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in RachelForster/Shinsekai?

Yes, RachelForster/Shinsekai currently has 9 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for RachelForster/Shinsekai 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.