deepsearch

To trace imports and dependencies during debugging, perform comprehensive codebase searches that read matched files and follow exports and consumers to map the full implementation path with cited file paths and line numbers.

The best way to search a repository for feature implementations is to apply broad search coverage for exact matches and variations, then synthesize primary locations, related files, and usage patterns with file paths and line numbers.

You can assess the impact of changing a shared utility by tracing where the concept appears, following connected dependencies, and mapping all connected usage across the repository to evaluate architecture impact.

Dependency tracing for an authentication flow works by searching for occurrences, reading matched files, following imports and exports to uncover the full implementation path, and presenting structured synthesis with cited locations.

Deepsearch is designed for large scale codebase exploration by systematically searching broad occurrences, following dependency paths, and eliminating incomplete or shallow searches to ensure connected files are not missed.