explore-codebase-cli

Trace Java microservices dependency chains by combining AST-based structural navigation with semantic vector search to map cross-service seams and call graphs. This approach captures structural relationships that traditional grep or vector-only search misses.

Find HTTP entry points in a Java codebase using graph-native primitives to identify routes and visualize call graphs. This structural navigation method maps distributed system boundaries more effectively than text search.

AST-graph code navigation works for impact analysis by querying a locally indexed LadybugDB graph to trace downstream callers and routes affected by changes in shared libraries. It provides deterministic structural queries across services.

Yes, you need a locally indexed LanceDB vector store and a LadybugDB graph to perform hybrid search. This setup enables semantic natural language lookups combined with structural filtering for precise codebase exploration.

Combine semantic search for intent with structural filtering for precision to locate all controllers within a specific microservice. This hybrid search leverages AST-based structural navigation alongside fuzzy natural language lookups.

Grep fails to capture service boundaries in distributed Java systems because it cannot model structural relationships like dependency chains and HTTP routes. Graph-native code intelligence combined with AST analysis is required to map cross-service seams.