diagnose

Root-cause analysis across multiple modules is performed by scoping investigations to architecture, bugs, performance, and dependencies. The process routes analyses to architectural agents for grounded reasoning and returns structured findings with evidence and file-context references.

Codebase architecture analysis evaluates trade-offs by routing reviews to Codex MCP or architectural agents. This produces structured findings grounded with evidence, including context files and references to support architectural decisions.

Debugging a stubborn performance issue across dependencies is handled by profiling the codebase and routing the analysis to grounded reasoning agents. It returns structured findings with evidence and file-context references to drive targeted fixes.

Yes, you can analyze codebases with complex dependency structures. It scopes investigations specifically across architecture, bugs, performance, and dependencies to deliver grounded, structured findings for complex projects.

Automated codebase analysis should be avoided for simple, isolated bugs where root-cause is immediately obvious. It is designed for complex projects requiring deep reasoning, architecture review, and performance profiling across multiple modules.

Yes, the diagnose Skill works with Codex MCP by routing architecture, bug, performance, and dependency analyses to it. This ensures grounded reasoning and returns structured findings with evidence and file-context references.