DeepSeek Harness 换肤 / 壁纸 / 主题包插件 (dsh-plugin) — 8 套 Mirage 主题、每用户强调色、壁纸2.0、主题包导入导出/分享链接、收藏与随机，纯原生 token 系统实现。
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 79%
Response Time: 2h
First Timer Success: 67%
RevolutionLA/dsh-dream-skin has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in RevolutionLA/dsh-dream-skin respond to incoming external pull requests in approximately 1.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 64.8 places RevolutionLA/dsh-dream-skin in the A tier.
The external contributor pull request merge rate for RevolutionLA/dsh-dream-skin is 79.3%, based on public PR activity from non-core contributors.
RevolutionLA/dsh-dream-skin does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
DeepSeek Harness 换肤 / 壁纸 / 主题包插件 (dsh-plugin) — 8 套 Mirage 主题、每用户强调色、壁纸2.0、主题包导入导出/分享链接、收藏与随机，纯原生 token 系统实现。
Collaborative maintainer environment in RevolutionLA/dsh-dream-skin. Reviews community pull requests with focus on project quality.
Discussions in RevolutionLA/dsh-dream-skin 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/RevolutionLA/dsh-dream-skin?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).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~9 hours (36% approval). Keep your diff compact for rapid review.
来由 10.6.1 验收轮（#70–#84 / #86–#94）逐条复核时，我用独立变异（不跑仓库自带的 mutation 用例，而是在隔离副本树里自己改源码/文档、再跑整套件）打了一圈。绝大多数翻红了，但有 5 处文档/口径声明改了以后整套件仍然绿或文档缺口。 它们都不是新功能缺陷，而是 #77 那一类问题的残余面：一个数字或一句声明被抄在两个地方，门只钉住其中一处。这类洞的危险不在今天错，而在它让"文档已被机检"这句话变得不准——读者（包括下一个改文档的人）会按"全部被钉住"来信任它。 验收方法本身也一并留档：隔离副本 = 工作树副本 + git init + 全量 git add（等价一次干净检出），基线整套件在该副本里 346/346 绿；然后每次只改一个文件、跑整套件（42s）、还原。判据是"整套件是否有任何一条红"，不是"我以为该红的那条"。 五处盲区（每条都给了可
结论 0.2.0-rc.2（当前 latest 通道，不是 alpha 才有的）把宿主"会话正文字号"的可选区间从 12–17 px 放宽到 10–22 px。我们不写对话字号（实测 lib/client.js 里 19 处 fontSize 全部是自家设置面板 UI 的固定值，如 3531: fontSize: "14px"、4196: fontSize: "13px"），所以这不是代码冲突。 真正的问题是：我们所有关于"可读"的结论，是在 12–17 这个区间内测出来的。宿主现在把下界推到 10px，把上界推到 22px，而我们的皮肤在最浅端 + 最透明的组合下从没在那两个极值上看过一次。这条开 issue 是为了给那两个极值补一次实测，不是为了改代码。 证据 宿主 @deepseek-ai/dsh-client-ui-theme/README.md，三版本实测（2026-10-06，grep -o "from 1[0-9] [a-z]* 1[0-9] px"）： 0.2.0-rc.1 from 12 to 17 px 0.2.0-rc.2 from 10 to 22 px ← 变化发生在 rc.2，即 latest 0.2.1-alpha.1 from 10 to 22 px rc.1 → alpha.1 的该段原
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 RevolutionLA/dsh-dream-skin, 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 RevolutionLA/dsh-dream-skin acknowledge new external contributions in approximately 1 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 79.3% were successfully merged into the primary branch.
RevolutionLA/dsh-dream-skin has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 64.8 places RevolutionLA/dsh-dream-skin in the Welcoming tier.
The external pull request merge rate is 79.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
RevolutionLA/dsh-dream-skin 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 RevolutionLA/dsh-dream-skin 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.