Cross-repository understanding using static analysis and selective AI
Cross-repository understanding using static analysis and selective AI
Built this because I kept losing context when working across multiple services. You know the problem: "what breaks if I change this auth function?" requires manually tracing through 5+ repositories to find all the dependencies. Technical approach: - Tree-sitter AST parsing for reliable dependency extraction across languages - Graph storage for efficient relationship traversal - AI only for semantic pattern matching on structured data (not raw code analysis) - Real-time impact analysis without the accuracy problems of pure semantic approaches Key insight: Don't trust AI for detailed code analysis (research shows 15-20% error rates), but use it for broader connections between components that static analysis has already verified. Differentiation from existing tools: - Sourcegraph: excellent single-repo navigation, limited cross-repo understanding - Glean: searches documentation, this analyzes actual code relationships - GitHub dependency graph: package-level tracking, this maps business logic flow Works whether you have microservices or complex monorepo with multiple domains. Planning to open source core components since existing solutions are enterprise-only. Early feedback welcome.
Share cardActual performance
Launch Intel predictions
Analyze your own launch →Correct prediction on native model
Similar products
perl-lsp – annotation free static analysis for Perl
Linting and static analysis of Clojure code
Smalisca – Static Code Analysis for Smali
Generate cli code in Go using static analysis
Static photoessay generator using gulp
DocComment – Code understanding tool using structural analysis and LLM
Cppcheck – A tool for static code analysis
The immutable repository
Unofficial Debian Sid Repository for Hyprland
Redu – ncdu for your restic repository