deepsearch

To search a codebase for a specific pattern, this tool identifies and enumerates all matching code locations across components, utilities, services, and hooks. It reads files, checks imports and exports, and returns a structured map of primary locations, related files, and usage patterns.

Tracing imports and exports across a repository requires reading files with matches and checking their connections. This approach follows the trail of what imports a concept and what it imports, synthesizing a map to identify the main implementation and related functionality.

Yes, you can use codebase search to map out implementation locations for components and hooks. It operates across multiple scopes including utilities and services to cover broad and deep searches, enforcing deterministic results by returning a prioritized map of matching files and references.

Deep code inspection handles related terms and variations by performing a broad search across common locations like components, utils, services, and hooks. It reads matching files to find connections and synthesizes a map of where the concept is used.

The limitations of deterministic codebase search for large repositories are not explicitly defined, but it enforces reproducible results by returning a structured map of primary locations, related files, and usage patterns across broad and deep search scopes.