scout

To analyze an unfamiliar codebase and extract constraints, you can bootstrap the repository to generate a CLAUDE.md file and decisions.sql artifacts. This process maps dependency constraints and test patterns so your implementation planning stays aligned with existing conventions.

Capturing codebase decisions and conventions for onboarding involves generating shared reference files like CLAUDE.md and decisions.sql. These artifacts record testable assertions and dependency constraints, ensuring new implementations respect the repository's established architectural patterns.

Yes, you can inspect a repository locally without web access by running an Explore agent. The agent maps relevant files, dependency constraints, and blast radius entirely offline, ensuring topic parsing and decision-memory queries execute securely within your local environment.

You can bootstrap a new repository by running the bootstrap command with the target repository path. This initializes the unfamiliar repo, producing CLAUDE.md, decisions.sql, and reference files that capture the shared conventions Claude needs for consistent implementation.

Yes, codebase constraint analysis works with research artifacts and clarification files by parsing them alongside the target topic. Supplying these artifacts when initiating the inspection ensures the Explore agent accurately maps relevant files and testable assertions for your specific implementation.

You should avoid local codebase inspection when your implementation planning requires external web data or real-time API lookups, as this approach operates entirely offline. It is designed for mapping local repository constraints, not gathering external documentation during the analysis phase.