analyse

To diagnose root causes in your codebase, provide an issue description to trigger a targeted investigation. The tool reads relevant files, analyzes patterns, and traces data flow to produce a structured diagnosis.

Codebase data-flow tracing tracks how data moves through your project to pinpoint where issues originate. You need it when debugging complex problems or analyzing patterns to identify the underlying root cause of unexpected behavior.

You can analyze code patterns across a project by running a targeted codebase investigation. This process reads relevant files and traces data flow to identify structural patterns and diagnose root causes.

You do not need any external dependencies to debug codebase issues, as this process requires only standard tooling. It operates without additional components to read files and generate structured analysis reports.

Codebase analysis reports are saved as markdown files in the reports/analysis/ directory, structured by date and topic. This structured diagnosis output ensures your investigation results are documented for future reference.

The best way to debug codebase issues without specialized components is to run a targeted investigation using standard tooling. It reads relevant files and traces data flow to output a structured root-cause diagnosis.