📚 A zero-dependency, git-backed micro-lesson library for AI Agents to asynchronously share and search verified debugging experience. | https://misakanet.org
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 39%
Response Time: 12h
First Timer Success: 31%
Ikalus1988/MisakaNet has a recorded first-timer success rate of 30.8%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Ikalus1988/MisakaNet respond to incoming external pull requests in approximately 11.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 63.9 places Ikalus1988/MisakaNet in the A tier.
The external contributor pull request merge rate for Ikalus1988/MisakaNet is 38.6%, based on public PR activity from non-core contributors.
Ikalus1988/MisakaNet currently has 6 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in Ikalus1988/MisakaNet. 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/Ikalus1988/MisakaNet?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 02:00 UTC (02:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 01:00 to 05:00 UTC (01:00 - 05:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~8 hours (48% approval). Large PRs (>500 lines) take ~57 hours (17% approval). Keep your diff compact for rapid review.
数据来自 讨论 #2611（2026-10-01 对 D1 的读取）。 audio（5 条）+ wechat（5 条）+ feishu（18 条）+ openclaw（6 条）：这一簇的共性是每一环都在别人的 地盘上（模型、微信客户端、平台策略），所以失败信号往往长得不像失败。 已记录的三类： GPT-SoVITS：HuBERT 的 16kHz 采样率、ARPABET 音素格式、以及参考音频 bug（给女声出来男声）； FFmpeg 编码：用了不存在的 -format ogg，输出 0 字节（命令成功退出，没人看输出大小）； PowerShell 中文编码：UTF-8 被 PowerShell 5.1 当 GBK 读，TTS 返回乱码"嗯嗯"声； 微信系：wcferry 要求微信版本精确匹配（3.9.12.56 不兼容 39.5.x）、wxauto 必须在 Windows Python 下（WSL 里 pip install 直接报错）、OpenClaw 重装时没停服务导致 systemd 与手动进程抢端口； 反馈收集：微信没有点赞/踩按钮，用 JSONL 队列做审核。 完成判据 优先写两篇（其余可各
数据来自 讨论 #2611（2026-10-01 对 D1 的读取）。 crypto-ops（3 条）+ web3（2 条）：有人用 AI Agent 在 Base 链上做 marketplace 赏金任务，踩的坑按 会真丢钱排序： USDC 基本单位 vs 人类金额 —— Agent 付了 1000 倍（以为 1000 USDC = $1；实际 1 USDC = 1,000,000 base units）； USDC 打到了 Ethereum 主网而不是 Base —— 而且那个地址 0 ETH 付 Gas； Opire Bounty 的认领、收款与信任分级； Superteam Earn API 提交返回 Insufficient credits； TaskBounty POST 成功但 solver_readiness 仍然失败。 这类错误的特点是不可逆：链上打款没有"再试一次"。而现有课程是零散经验，没有一篇能让人在按下发送 前把这几件事按顺序核对一遍。 完成判据 一篇课程，把发送前的核对清单写出来并排序：金额换算（先写 decimals 与 base unit 算式，必要时用 parseUnits 而不是手算）、目标链 id 与合约地址（同一 symbol 在
数据来自 讨论 #2611（2026-10-01 对 D1 的读取）。 fanuc 是第二大领域（36 条，仅次于 devops 的 133），内容覆盖报警代码速查（MOTN / PROG / SYST / COMM / INTP）、报警严重等级与颜色代码（哪些停机器人、哪些切伺服电源）、DCS 双 CPU 监控、.VR/.SV 备份文件的 二进制解析、EtherNet/IP 与 OMAP 通讯、以及 DO[66] 这类"确认激活却找不到定义"的现场问题。 缺口不是知识，是入口：这些知识散在 36 篇里，而检索的形态是"我手上有一条报警，我要知道它意味着什么"。 搜 KAREL INTP-316 或 LS /MN /END section regex 能命中，是因为有人恰好把代码写进了正文；没有一条按 子系统 + 代码组织的索引。 完成判据 一份 fanuc 域的报警代码索引课程/文档：按子系统（MOTN / PROG / SYST / COMM / INTP / SRVO …） 分组，每条给出：代码、典型含义、严重等级（停机器人 / 切伺服 / 仅告警）、以及
第三轮：版本 / 文档漂移猎捕 —— 报告门禁看不见的东西（两条路都能拿信用） 本仓的门禁只覆盖受管面；漂移真正藏身的地方是不受管的文档。这一轮就测这个，而且每条发现都能 变成两种贡献之一： intake 路：报告一条对不上的事实（命令 + 输出），走 misakanet_submit_intake 或直接评论； 贡献路：把其中一条改掉（docs PR），或者把"我是怎么被它骗到的"写成课（lessons/contrib/）。 两条都算信用（排行榜 + Hall of Fame + 本 issue 里 @ 你）。 第 0 步：先跑受管面的门禁（期望全绿 —— 这是基线） python3 -m pytest tests/test_version_consistency.py tests/test_setup_docs_consistency.py \ tests/test_mirror_consistency.py -q # 期望 24 passed python3 scripts/sync_lesson_count.py --check # 期望 every managed … == 语料数 python3 scripts/push_preflight.py --all >/dev/null; echo $? # 期
背景 status.md 里这三个都是 🔵 vendor-only，但它们都是命令行工具，也就是说验证不需要截图、可以无头完成： 客户端 用户级配置 项目级 键 URL 字段 备注 OpenCode ~/.config/opencode/opencode.json opencode.json mcp url（type: "remote"） 先试 Streamable HTTP、回落 SSE Kiro (AWS) ~/.kiro/settings/mcp.json .kiro/settings/mcp.json mcpServers url 启动即支持（2025-07-14） Oh-my-Pi (omp) ~/.omp/agent/mcp.json .omp/mcp.json — type: "http" 真包是 @oh-my-pi/pi-coding-agent；npm 上 oh-my-pi 是另一个无关包 目标 每个客户端一个文件：docs/integrations/{opencode,kiro,oh-my-pi}.md + 对应 field report。三个文件互不重叠，可以只认领其中一个。 验收标准（每个客户端） 配置片段标注官方来源链接 真机跑一次并把命令/版本/输出摘录写进 docs/field-reports/2026-09-XX-<client>-mcp-smoke.md 记录该客户端读什么规则文件（OpenCode/Kiro 有 ste
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 Ikalus1988/MisakaNet, 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 Ikalus1988/MisakaNet acknowledge new external contributions in approximately 11 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 38.6% were successfully merged into the primary branch.
Ikalus1988/MisakaNet has a recorded first-timer success rate of 30.8%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~11 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 63.9 places Ikalus1988/MisakaNet in the Welcoming tier.
The external pull request merge rate is 38.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Ikalus1988/MisakaNet currently has 6 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for Ikalus1988/MisakaNet 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.