analyze

To analyze code architecture, gather context, evaluate dependencies, map execution flows, identify bottlenecks, and assess security implications. This structured approach ensures repeatable results across projects of any size by following a four-phase protocol.

Debugging issues and assessing security vulnerabilities requires systematically gathering context, mapping execution flows, and evaluating dependencies. This process synthesizes key findings into concise, actionable recommendations for remediation.

Yes, performance profiling applies across projects of any size using a four-phase protocol: gather context, analyze systematically, synthesize findings, and provide recommendations. This ensures repeatable results for complex performance bottlenecks.

Code review analysis works without specific framework dependencies because it operates through a structured four-phase protocol. It evaluates dependencies, maps execution flows, and produces actionable results regardless of the underlying technology stack.

An architecture review produces a concise summary, key findings, in-depth analysis, and prioritized recommendations for remediation. This actionable output directly results from synthesizing systematically gathered context and evaluated dependencies.

You should not use a systematic four-phase protocol for issue analysis when you require rapid, ad-hoc fixes instead of thorough evaluation. The protocol gathers context and synthesizes findings, which demands more time than quick patches.