github-monolith-navigator

You locate code in a Rails monolith by browsing the /packages/ directory and utilizing package.yml metadata to pinpoint the module responsible for the target feature, reducing exploration time across 140+ packages.

Yes, you can locate controllers, models, tests, or routes across the codebase using targeted semantic searches. It applies code discovery tasks spanning /workspaces/github and the packages/ directory to identify specific file definitions.

Mapping dependencies between packages in a monolithic repository is achieved by leveraging package.yml metadata and direct file references. This context-aware exploration enables fast code comprehension by showing where a symbol is implemented or tested.

Yes, this code navigation approach works for identifying where a class is implemented and tested. It satisfies semantic search and developer guidance by mapping dependencies and locating symbols across the monolith using package.yml metadata.

To locate a specific file definition in a monolith with 140+ packages, ask the assistant to locate where the file is implemented. It leverages package.yml metadata and direct file references to answer where a file defines a specific element.