tirth8205/code-review-graph：README 来源编辑指南

tirth8205/code-review-graph 的 README 将项目描述为"Local-first code intelligence graph for MCP and CLI. Builds a persistent map of your codebase so AI coding tools read only what matters, with benchmarked context reductions on reviews and large-repo workflows."。本文只整理仓库能直接核验的内容，不把星标、Fork 或宣传语当成质量证明。README 在"README"下的说明是：AI coding tools can end up re-reading large parts of your codebase on review tasks. code-review-graph fixes that. It builds a structural map of your code with Tree-sitter so it reads only what matters.。这给出的首先是项目边界，而不是已经完成的生产验证。

从 README 的"Limitations and known weaknesses"和相关条目看，读者可以先判断它是否解决自己的具体问题：Small single-file changes: Graph context can exceed naive file reads for trivial edits (see express results above). The overhead is the structural metadata that enables multi-file analysis.。如果你的目标与这段说明不一致，就不应仅凭项目热度采用它。这里保留原项目名、命令和组件名，方便回到一手来源核对。 README 还列出了另一条可核对的信息：Impact "recall 1.0" is graph-derived and circular: the historical ground truth comes from the same graph edges the predictor walks, so it is an upper bound by construction.。这类原文条目可以帮助读者设计试运行步骤，但不能代替自己的环境测试。

README 把工作方式分散写在"Quick Start"等段落中。可确认的线索包括：Requires Python 3.10+. For the best experience, install uv.。这篇整理没有把未写出的架构、性能或安全边界补成结论；真正的运行链仍应结合仓库目录、配置文件和版本标签检查。

第一次安装应从 README 给出的入口开始。当前可复核的命令是： pip install code-review-graph # or: pipx install code-review-graph code-review-graph install # auto-detects and configures all supported platforms code-review-graph build # parse your codebase 如果仓库没有提供命令，本文不会替它编造安装步骤，而是建议先打开 README 的"How It Works"部分，确认系统依赖、默认端口和首次初始化动作。

日常使用的细节取决于项目实际文档。README 的"Quick Start"段落提到：To remove CRG from a Git or SVN project, use the symmetric uninstall command from anywhere inside its working tree. The target is normalized to the working tree root, and non-repository directories are refused.。对于配置文件、环境变量、权限和数据目录，当前稿只记录来源明确的部分；未写明的默认值必须在测试环境中验证，并保留可回滚的配置副本。 同一部分还提到：Search quality (MRR 0.35): Keyword search finds the right result in the top-4 for most queries, but ranking needs improvement. Express queries return 0 hits due to module-pattern naming.。