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.

Источник