Struggling to Track Changes Across Repositories? Meet Where am I
🇻🇳 Tóm tắt: Where am I là một công cụ mã nguồn mở, local-first dành cho nhóm sinh viên và nhóm phát triển nhỏ. Công cụ giúp theo dõi tác động của thay đổi mã trên nhiều repository mà không cần tải mã nguồn lên dịch vụ bên ngoài. Tính năng tóm tắt thay đổi bằng LLM và khả năng phân tích trực tiếp các tệp làm việc cục bộ ngay cả khi không sử dụng Git đang được phát triển.
When a project grows across several repositories, a small code change can affect an API, a service, a database, or a test somewhere else. Following that chain manually is slow, especially for university teams and small development teams without dedicated platform tooling.
I built Where am I to make that work easier.
What it is
Where am I is an open-source, local-first impact graph for understanding how code changes move through a system. It analyzes repositories on your machine and visualizes relationships between files, APIs, services, databases, and tests.
The goal is simple: help a developer answer “What could this change affect?” before a pull request is merged.
What it can do today
- Visualize code paths affected by the current working-tree diff.
- Surface brief API and schema changes from teammates’ pull requests and remote commits.
- Connect API paths, handlers, wrappers, OpenAPI documents, and tests.
- Search a combined API catalog across multiple repositories.
- Trace functions, databases, external APIs, and error codes back to files and evidence lines.
- Provide repository structure and system summaries for onboarding.
Why local-first?
Source code can contain business logic, credentials, internal endpoints, and other sensitive information. Where am I is designed to analyze local Git repositories without requiring teams to upload their code to an external service.
You still need to review generated snapshots before sharing them, but the default workflow keeps analysis close to the source.
Who I built it for
I especially want this to help:
- university project teams,
- small product and development teams,
- contributors joining an unfamiliar codebase,
- developers working across multiple repositories.
What I am building next
I want to keep expanding the project based on real team needs. An LLM-powered summary of code changes is currently in development, with the goal of turning impact evidence into a concise explanation that teams can review quickly.
I am also developing a way to detect and explain changes directly from local working files, even when a project is not using Git. This should make the tool useful for more lightweight and early-stage workflows.
I am also interested in improving repository integrations, impact accuracy, onboarding workflows, and multilingual support.
Feedback and contributions are welcome
If you try the project, please share what was confusing, what worked, and what your team needs next. Feature requests and bug reports can be opened as GitHub issues. If you are interested in using, testing, or contributing to the project, feel free to contact me.
All rights reserved
