analyze

To identify recurring incident patterns, run a pattern recognition analysis across your codebase and incident artifacts. This process scans historical incidents to detect recurring hotspots, scores risks, and produces a structured Markdown report with actionable findings.

A system health assessment is a strategic analysis that scans code, docs, and artifacts to surface reliability, performance, and architectural risks. It builds a discovery-driven system map to evaluate structural health proactively rather than reacting to incidents.

You perform an architecture review with interactive checkpoints by running a multi-mode analysis across your repository. This assesses architectural risks inline, evaluates design trade-offs, and determines whether a finding requires a design-level escalation or a point fix.

You need to escalate a codebase risk for architectural redesign when analysis detects systemic issues requiring design-level trade-offs rather than point fixes. The system flags these scenarios, recommends a deeper design workflow, and generates an escalation report.

Yes, you can analyze project documentation and code files without external dependencies. The system requires read access to project files and incident artifacts to search code, build a system map, and generate structured Markdown reports independently.

The best way to generate a structured risk assessment report is to run a comprehensive system analysis that scores risks and detects patterns. This produces a prioritized Markdown document with escalation recommendations suitable for tracking and team handoff.