diagnose

Name: diagnose
Availability: InStock
Author: Junghwan

Analyze codebase architecture, bugs, performance, and dependencies with structured findings.

Updated Feb 14, 2026

Search Tags:#architecture #performance #debugging #codebase #dependencies #analyze #root-cause

Ready to run

npx skills add https://github.com/shaun0927/codex-superskills --skill diagnose-shaun0927

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/shaun0927/codex-superskills/tree/main/skills/analyze
Command: npx skills add https://github.com/shaun0927/codex-superskills --skill diagnose-shaun0927

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep analysis of architecture, bugs, performance issues, and dependencies, delivering grounded, structured findings to drive fixes and improvements.

Core Features & Use Cases

Routes analyses to Codex MCP or architectural agents for grounded reasoning.
Produces structured findings with evidence, including context files and references for decisions.
Scopes investigations across architecture, bugs, performance, and dependencies for complex systems.
Use cases: debugging a stubborn performance issue, performing root-cause analysis, evaluating architecture trade-offs.

Quick Start

Provide a deep analysis of the current codebase focusing on architecture, bugs, performance, and dependencies.

Frequently Asked Questions about diagnose

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I perform root-cause analysis across multiple modules in a complex codebase?▼

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.

What is the best way to analyze codebase architecture and evaluate trade-offs?▼

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.

How do I debug a stubborn performance issue that spans multiple dependencies?▼

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.

Can I use this to analyze codebases with complex dependency structures?▼

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.

When should I not use automated codebase analysis for debugging?▼

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.

Does the diagnose Skill work with Codex MCP for grounded reasoning?▼

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.