Struggling to keep up with team changes across repositories? I built a local-first impact graph

说明与用途

Where am I 是一个本地优先的工具，帮助开发者可视化 API 更改在多仓库中的影响路径，提供基于证据的交互式影响图，提升代码评审效率。

问题

In multi-repository systems, a single API change can ripple through many components, making it hard to track downstream effects during code review.

结果

The tool provides a visual, evidence-backed view of how a change propagates across multiple repositories, improving review efficiency and reducing missed downstream effects.

工作流

• Configure repository roots and options in whereami.config.json
• Run the Node.js scanner to collect diffs, status, and static facts
• Scanner extracts functions, API paths, database calls, docs, tests, and error codes
• Scanner connects facts into an evidence graph and writes a local snapshot
• React/XYFlow UI renders the graph, allowing filtering by current work, team changes, or API contracts
• Select nodes/edges to view source evidence, diffs, and suggested checks
• Use the graph to answer review questions and identify impacted areas

证据

Where am I is an early MVP. Its output is supporting evidence for review, not a replacement for tests, security checks, or engineering judgment.

来源

The scanner reads the source code in the repositories you configure. Its local configuration and generated snapshot may contain absolute paths, repository names, branches, commit messages, pull request titles, function names, API paths, and evidence lines.

来源