README 证据

<!-- mcp-name: io.github.detailobsessed/codereviewbuddy -->

codereviewbuddy

    

An MCP server that helps your AI coding agent manage PR review comments from any AI reviewer that uses GitHub's PR review infrastructure.

Features

Review comment management

• Triage review comments — triage_review_comments filters to only actionable inline threads and includes direct GitHub URLs for each comment
• Get thread details — get_thread fetches full conversation history for any thread by node ID
• Reply to anything — inline review threads (PRRT_), PR-level reviews (PRR_), and bot issue comments (IC_) all routed to the correct GitHub API

CI & stack diagnosis

• Diagnose CI failures — diagnose_ci collapses 3-5 sequential gh commands into one call: finds the failed run, identifies failed jobs/steps, and extracts actionable error lines
• Stack activity feed — stack_activity shows a chronological timeline of pushes, reviews, labels, merges across all PRs in a stack with a settled flag for deciding when to proceed
• Scan merged PRs — list_recent_unresolved catches late review comments on already-merged PRs

Agent experience

• Recovery-guided errors — every tool handler classifies errors (auth, rate limit, not found, workspace, GraphQL, config) and returns actionable recovery hints so agents self-correct instead of retrying blindly
• Next-action hints — tool responses include next_steps suggestions guiding agents to the right follow-up tool call
• Empty result messages — when results are empty, responses explain why and suggest what to try next
• GUI URLs — triage items include comment_url so agents can link users directly to the comment on GitHub
• **Tool classification tag

[excerpt truncated]

已选源码清单

• README.md
• pyproject.toml
• src/codereviewbuddy/__init__.py
• src/codereviewbuddy/_instance.py
• src/codereviewbuddy/cache.py
• src/codereviewbuddy/cli.py
• src/codereviewbuddy/config.py
• src/codereviewbuddy/gh.py
• src/codereviewbuddy/github_api.py
• src/codereviewbuddy/install.py
• src/codereviewbuddy/models.py
• src/codereviewbuddy/server.py

资料来源：README.md:1-120

资料来源：README.md:1-120

• .: README.md, pyproject.toml
• src: src/codereviewbuddy/__init__.py, src/codereviewbuddy/_instance.py, src/codereviewbuddy/cache.py, src/codereviewbuddy/cli.py, src/codereviewbuddy/config.py, src/codereviewbuddy/gh.py

资料来源：pyproject.toml:1-120

• Documentation signal: README.md
• Runtime/package signal: pyproject.toml
• Source inspection signal: src/codereviewbuddy/__init__.py
• Source inspection signal: src/codereviewbuddy/_instance.py
• Source inspection signal: src/codereviewbuddy/cache.py
• Source inspection signal: src/codereviewbuddy/cli.py
• Source inspection signal: src/codereviewbuddy/config.py
• Source inspection signal: src/codereviewbuddy/gh.py
• Source inspection signal: src/codereviewbuddy/github_api.py
• Source inspection signal: src/codereviewbuddy/install.py

资料来源：src/codereviewbuddy/__init__.py:1-120

Pitfall Log / 踩坑日志

项目：detailobsessed/codereviewbuddy

摘要：发现 6 个潜在踩坑项，其中 0 个为 high/blocking；最高优先级：能力坑 - 能力判断依赖假设。

1. 能力坑 · 能力判断依赖假设

• 严重度：medium
• 证据强度：source_linked
• 发现：README/documentation is current enough for a first validation pass.
• 对用户的影响：假设不成立时，用户拿不到承诺的能力。
• 建议检查：将假设转成下游验证清单。
• 防护动作：假设必须转成验证项；没有验证结果前不能写成事实。
• 证据：capability.assumptions | mcp_registry:io.github.detailobsessed/codereviewbuddy:0.37.0 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.detailobsessed%2Fcodereviewbuddy/versions/0.37.0 | README/documentation is current enough for a first validation pass.

2. 维护坑 · 维护活跃度未知

• 严重度：medium
• 证据强度：source_linked
• 发现：未记录 last_activity_observed。
• 对用户的影响：新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。
• 建议检查：补 GitHub 最近 commit、release、issue/PR 响应信号。
• 防护动作：维护活跃度未知时，推荐强度不能标为高信任。
• 证据：evidence.maintainer_signals | mcp_registry:io.github.detailobsessed/codereviewbuddy:0.37.0 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.detailobsessed%2Fcodereviewbuddy/versions/0.37.0 | last_activity_observed missing

3. 安全/权限坑 · 下游验证发现风险项

• 严重度：medium
• 证据强度：source_linked
• 发现：no_demo
• 对用户的影响：下游已经要求复核，不能在页面中弱化。
• 建议检查：进入安全/权限治理复核队列。
• 防护动作：下游风险存在时必须保持 review/recommendation 降级。
• 证据：downstream_validation.risk_items | mcp_registry:io.github.detailobsessed/codereviewbuddy:0.37.0 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.detailobsessed%2Fcodereviewbuddy/versions/0.37.0 | no_demo; severity=medium

4. 安全/权限坑 · 存在评分风险

• 严重度：medium
• 证据强度：source_linked
• 发现：no_demo
• 对用户的影响：风险会影响是否适合普通用户安装。
• 建议检查：把风险写入边界卡，并确认是否需要人工复核。
• 防护动作：评分风险必须进入边界卡，不能只作为内部分数。
• 证据：risks.scoring_risks | mcp_registry:io.github.detailobsessed/codereviewbuddy:0.37.0 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.detailobsessed%2Fcodereviewbuddy/versions/0.37.0 | no_demo; severity=medium

5. 维护坑 · issue/PR 响应质量未知

• 严重度：low
• 证据强度：source_linked
• 发现：issue_or_pr_quality=unknown。
• 对用户的影响：用户无法判断遇到问题后是否有人维护。
• 建议检查：抽样最近 issue/PR，判断是否长期无人处理。
• 防护动作：issue/PR 响应未知时，必须提示维护风险。
• 证据：evidence.maintainer_signals | mcp_registry:io.github.detailobsessed/codereviewbuddy:0.37.0 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.detailobsessed%2Fcodereviewbuddy/versions/0.37.0 | issue_or_pr_quality=unknown

6. 维护坑 · 发布节奏不明确

• 严重度：low
• 证据强度：source_linked
• 发现：release_recency=unknown。
• 对用户的影响：安装命令和文档可能落后于代码，用户踩坑概率升高。
• 建议检查：确认最近 release/tag 和 README 安装命令是否一致。
• 防护动作：发布节奏未知或过期时，安装说明必须标注可能漂移。
• 证据：evidence.maintainer_signals | mcp_registry:io.github.detailobsessed/codereviewbuddy:0.37.0 | https://registry.modelcontextprotocol.io/v0.1/servers/io.github.detailobsessed%2Fcodereviewbuddy/versions/0.37.0 | release_recency=unknown