investigate

To investigate a codebase, consult llmdoc-first documentation by reading the index, overview, architecture, and guides before inspecting code. This approach uses Glob and Grep to gather information and returns concise findings directly without persisting files.

Exploring codebase structure across repositories is best handled by querying llmdoc-driven documentation first. This method reads documented references and uses Glob, Grep, and Read to produce structured, actionable findings for engineering decisions.

Yes, you can get codebase insights without persisting files. The investigation process reads llmdoc documentation and source code directly, delivering report-ready outputs and concise findings in conversation without creating any new files.

Yes, codebase investigation works with llmdoc references by design. It prioritizes reading the llmdoc index, overview, architecture, and guides to answer questions about codebase behavior before falling back to Glob and Grep on source code.

A documentation-first codebase investigation relies on the accuracy and completeness of existing llmdoc files. If documentation is outdated or missing, the tool must fall back to searching code with Glob and Grep, which may yield less structured findings.