/grok

To understand an unfamiliar codebase before editing, you can generate a read-only walkthrough that maps entry points, data models, hot paths, and tests. This investigation provides concrete file:line citations for quick navigation without modifying code.

Mapping an authentication flow requires a question-driven read-only investigation that scopes the request into an actionable plan. The walkthrough identifies high-signal files and provides file:line references to explain the persistence behavior and core logic.

Identifying data models and persistence behavior involves reading relevant repository entry documents and selecting high-signal files. The walkthrough focuses on core types and hot paths, optionally persisting findings as a study artifact for future reference.

Yes, you can perform a read-only code investigation to understand repository navigation and test organization without modifying files. The process gathers entry points and walks important layers to explain why files exist and how tests are structured.

Turning a vague request into an actionable plan requires question-driven scoping. The investigation narrows the focus to relevant entry documents, core data models, and hot paths, producing a concise summary with file:line references for immediate follow-up.

Yes, reading repository entry documents is required to understand code structure effectively. The walkthrough process selects a small set of high-signal files based on these documents to explain core types, hot paths, and test organization.