analyze

Perform a read-only analysis to understand architecture without modifying the code. This approach provides evidence-based conclusions and ranked explanations of behavior across modules, ensuring the underlying codebase remains unaltered.

Evidence-based code analysis is a deep examination providing a ranked synthesis of explanations with explicit confidence levels. It distinguishes between direct evidence and inferred conclusions to explain exactly why a feature behaves in a certain way.

Analyze the repository for insights on the error handling pattern to understand its implementation across modules. This reveals workflow implementation and causality across the codebase using ranked explanations based on direct evidence.

Yes, this codebase analysis explicitly distinguishes between direct evidence and inferred conclusions. It provides a ranked list of explanations with confidence levels so you can clearly identify proven facts versus inferred behavior.

Perform a deep, read-only architectural analysis to get codebase insights for complex dependencies. This yields a ranked synthesis of explanations with explicit confidence levels and evidence-based conclusions about workflow causality.

Use read-only codebase analysis when you need to understand behavior, architecture, and causality without altering the code. It is ideal for safely gaining evidence-based insights when you must avoid introducing changes to the repository.