investigation

To investigate a codebase, systematically scan the repository structure and key files like README.md to map dependencies and implementation patterns. This process generates an investigation report and risk analysis artifacts to inform safe code changes.

Codebase risk analysis is the process of identifying implementation patterns and potential risk factors in a repository. You need it before modifying software projects to ensure structured discovery, document existing dependencies, and generate artifacts that inform safe changes.

The best way to generate documentation for an unfamiliar project is to run a structured discovery workflow that scans repository structure and key files like AGENTS.md. This produces comprehensive investigation reports that map dependencies and document codebase context.

Yes, codebase investigation applies to software projects of any size. The structured discovery workflow scales to map repository structures, locate essential files like CLAUDE.md, and identify dependencies regardless of the overall scale of the codebase.

To identify dependencies and implementation patterns, scan the repository structure and essential files such as README.md. This systematic investigation maps related patterns and dependencies, producing a risk analysis report for stakeholders.

The investigation workflow relies on scanning repository structures and key files like README.md, AGENTS.md, and CLAUDE.md. If these specific files are absent or lack documentation, the generated investigation report and risk analysis may have limited context.