HunterCode · Community Edition · 腾讯 WorkBuddy 金融版的开源本地替代方案 · open-source, local alternative to Tencent WorkBuddy Finance Edition · 多智能体投研终端 A股/港股/美股 · 推理在你机器上跑 · 仓位不出你硬盘 · BYOK · Apache 2.0 · docker compose 自托管
C-Rank Grade: A (Welcoming) - 62/100
External PR Merge Rate: 70%
Response Time: 2d
First Timer Success: 50%
agentpit-io/hunter-community has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in agentpit-io/hunter-community respond to incoming external pull requests in approximately 52.7 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 61.8 places agentpit-io/hunter-community in the A tier.
The external contributor pull request merge rate for agentpit-io/hunter-community is 70.0%, based on public PR activity from non-core contributors.
agentpit-io/hunter-community currently has 9 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
HunterCode · Community Edition · 腾讯 WorkBuddy 金融版的开源本地替代方案 · open-source, local alternative to Tencent WorkBuddy Finance Edition · 多智能体投研终端 A股/港股/美股 · 推理在你机器上跑 · 仓位不出你硬盘 · BYOK · Apache 2.0 · docker compose 自托管
Collaborative maintainer environment in agentpit-io/hunter-community. Reviews community pull requests with focus on project quality.
Discussions in agentpit-io/hunter-community 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/agentpit-io/hunter-community?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 Monday - Wednesday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~34 hours (88% approval). Large PRs (>500 lines) take ~253 hours (32% approval). Keep your diff compact for rapid review.
背景 docs/env-samples/.env.claude.example 写的是： LLM_PROVIDER=anthropic LLM_BASE_URL=https://api.anthropic.com # 无 /v1 后缀 LLM_DEFAULT_MODEL=claude-sonnet-4-6 LLM_SCHEMA_SANITIZE=0 但 scripts/opencode/gen-config.py 生成对话引擎配置时只读取 LLM_BASE_URL、LLM_API_KEY、LLM_DEFAULT_MODEL、LLM_SCHEMA_SANITIZE，并固定使用 @ai-sdk/openai-compatible，不读 LLM_PROVIDER。照模板填写，对话引擎会用 OpenAI 兼容协议去请求一个不带 /v1 的 Anthropic 地址，大概率无法工作。该模板头部也标注「待评测」。矩阵里已实测可用的 Claude 路径是经 AIHubMix 网关（OpenAI 兼容）。 要做的事（二选一，先在 issue 里说明打算走哪条） A. 实测 Anthropic 官方的 OpenAI 兼容端点能否跑通对话 + 工具调用；能则把模板改成该写法并标注实测日期 B. 让 gen-config.py 在 LLM_PROVIDER=anthropic 时生成 Anthropic 原生 provider 配置（需确认对话引擎镜像内是否
背景 data/hk_master.csv（3226 条，更新至 2026-08-19）由 scripts/gen_hk_master_csv.py 从港交所官方 ListOfSecurities.xlsx 生成，只有英文名。脚本注释明确写了「不假装有中文名」「错的中文名会让人下错单」——所以这个 issue 不接受任何非官方来源的翻译或第三方对照表。 要做的事 核实港交所是否公开发布中文版证券列表（与英文版同代码、同更新频率） 若有：扩展 gen_hk_master_csv.py，按股票代码合并出 name_zh 列；代码对不上的留空，不做模糊匹配 若没有：在 issue 里回报核实结果（附官方页面链接），关闭 issue 涉及文件 scripts/gen_hk_master_csv.py、data/hk_master.csv apps/api/app/services/source_catalog.py（hk.master 条目的 note 需同步） 验收标准 数据来源为港交所官方文件，PR 里写明下载地址与日期 抽查 20 只（含 00700、09988、02318 等），中英文名与港交所网站一致 name_zh 为
背景 scripts/ 下有 6 个自检脚本：check_skill_sync.py、check_skill_tools.py、check_source_upstream.py、check_sources.py、check_tool_prompts.py、check_tools.py。README 常见问题里推荐用 check_skill_sync.py，但 6 个脚本都没有 argparse，--help 看不到用途、前置条件（要不要容器在跑、要不要平台 key）和参数。 涉及文件：上述 6 个脚本；新建 docs/dev-scripts.md 期望产出 每个脚本加 argparse，--help 输出一句话用途 + 前置条件 + 现有参数（不改检测逻辑） docs/dev-scripts.md 汇总 6 个脚本各自什么时候用 验收标准 6 个脚本 python scripts/xxx.py --help 均正常输出且退出码 0 不带 --help 时行为与改动前一致（PR 里贴改动前后各跑一次的输出） 预估时长：2 小时
背景 apps/api/ 根目录下有 7 个一次性调试脚本，已入库但全仓无引用（grep 核实；akshare_impl.py 里的 fetch_quote 是 agents/data_sources/akshare_quote.py 的同名函数，与根目录文件无关）： fetch_eastmoney.py fetch_quote.py fetch_stock.py parse_fundflow.py parse_fundflow2.py search_fund.py search_fund_flow.py 其中 fetch_quote.py 写死了 2026-05-09 的日期和单只股票代码，search_fund.py 依赖 duckduckgo_search。它们会被 COPY . /app 打进 api 镜像，也会让新贡献者误以为是入口文件。 涉及文件：上述 7 个文件；apps/api/Dockerfile（只读，确认没有单独引用） 期望产出：删除这 7 个文件。 验收标准 grep -rn "fetch_eastmoney\|parse_fundflow\|search_fund" --include='*.py' . 除 _fetch_eastmoney 函数外无结果 CI 的 API 导入冒烟通过 预估时长：30 分钟
背景 对话里可以说「帮我扫一下 A 股低估值超卖的股票」，模型会调用 screener_market_screen 工具。它有 7 个预设：uptrend、value_oversold、breakout_volume、hk_dividend、rs_line_up、vcp_range、fomo_short，还支持用户自己写 thinkScript 子集脚本。但这些只写在工具描述和代码里，没有面向用户的文档（docs/screener-test-cases.md 是测试用例，不是使用说明）。 涉及文件 scripts/opencode-mcp/screener_mcp.py（语法说明 _SYNTAX、预设列表、4 条使用边界） apps/api/app/services/quant/screen_source.py（PRESETS 列表：每个预设的市场与脚本原文） 新建 docs/screener-presets.md 期望产出 每个预设一节：适用市场、筛选逻辑（中文解释 + 脚本原文）、适合问什么问题；末尾写清使用边界（数据延迟 15 分钟、不能用于回测、market_cap_basic 口径差异、skipped_incomplete 的含义）。 验收标准 7 个预设的市场与脚本和
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 agentpit-io/hunter-community, 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 agentpit-io/hunter-community acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 70.0% were successfully merged into the primary branch.
agentpit-io/hunter-community has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 days+. 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 61.8 places agentpit-io/hunter-community in the Welcoming tier.
The external pull request merge rate is 70.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, agentpit-io/hunter-community currently has 9 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for agentpit-io/hunter-community 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.