ChangeLens

Developers often know which file they changed, but not everything else that may need attention because of that change. A Git diff shows the direct changes between two revisions, but related source files, tests, documentation, configuration, and API consumers may also be affected. Finding those connections manually takes time and can lead to missed follow-up work. ChangeLens is a developer workflow tool that helps answer a practical question: “I changed this code — what else should I look at?” ChangeLens compares two Git revisions and builds a structured change set. It then analyzes relationships between changed files and other repository artifacts, including source references, API consumers, tests, documentation, and configuration. Finally, it compares the discovered relationships against the actual change set to determine whether related artifacts were also updated. The result separates three useful states: changed files, affected-and-changed artifacts, and potentially missing artifacts. Each relationship can include its type, supporting evidence, and confidence level. This makes the result reviewable rather than presenting unexplained guesses. A potentially missing artifact is intentionally treated as something for developer review, not as a guaranteed required change. The target users are developers and engineering teams performing maintenance, refactoring, bug fixes, and change reviews. A developer provides a repository path and two Git revisions through the ChangeLens dashboard. The React and Vite frontend sends the request to a FastAPI backend, which runs the deterministic analysis pipeline and presents the resulting completeness report. The core workflow is: Change Detection → Relationship Discovery → Completeness Analysis → Developer Action What makes ChangeLens different is its focus on change-aware completeness rather than generic code review. It connects the current change with relationships already present in the repository and shows the evidence behind each finding. We verified the implementation with 40 backend/analyzer tests, 9 frontend tests, a successful production build, and deterministic scenarios covering complete and potentially incomplete changes. ChangeLens is currently a local, deterministic MVP and does not claim remote GitHub analysis, LLM-based analysis, or autonomous code modification.