skills.rest
KYRIE66nb
KYRIE66nbCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

analyze

Analyze codebases for architecture, bug, and performance issues with evidence-backed root-cause findings.

Updated Apr 8, 2026
Search Tags:#architecture#performance#dependencies#bugs#investigate#analyze#root-cause
One-click install
npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill analyze-kyrie66nb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyze
Source: https://github.com/KYRIE66nb/codex-omx-public-config/tree/main/home/.agents/skills/analyze
Command: npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill analyze-kyrie66nb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep analysis and investigation of architecture, bugs, performance issues, and dependencies. It routes to the architect agent or Codex MCP for thorough analysis and returns structured findings with evidence.

Core Features & Use Cases

  • Route to architect agent or Codex MCP for thorough analysis and evidence-backed findings.
  • Provide context files to the analysis tool for grounded reasoning.
  • Return structured findings with file references and actionable recommendations.

Quick Start

Describe the analysis target and request a structured root-cause report with file references.

Frequently Asked Questions about analyze

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

FAQPage Schema
How do I investigate root-cause bugs across multiple files in a complex codebase?▼

Root-cause bug investigation across multiple files is performed by routing context files through Codex MCP to analyze cross-file reasoning and dependency impacts, returning evidence-backed findings with specific file references.

Can I analyze architecture and performance issues without providing source files?▼

Architecture and performance analysis requires access to relevant context files such as source files and configs. Providing these inputs grounds the reasoning process and ensures the returned findings contain accurate file references.

What's the best way to assess dependency impacts in a complex system?▼

Dependency impact assessment is handled by routing the codebase context to the architect agent or Codex MCP, which evaluates cross-file reasoning and returns structured findings with actionable recommendations.

How does deep system analysis work when integrated with Codex MCP?▼

Deep system analysis works by routing analysis targets and relevant context to Codex MCP, which performs multi-file context evaluation and generates structured root-cause reports with evidence-backed file references.

When do I need structured findings with file references for codebase investigation?▼

Structured findings with file references are needed when complex system issues require cross-file reasoning and dependency impact assessments, providing actionable recommendations grounded in specific source file evidence.

Does this analysis approach work for complex systems requiring cross-file reasoning?▼

This analysis approach is specifically designed for complex systems where issues require cross-file reasoning, multi-file context, and dependency impact assessments, routing deep analysis through the architect agent or Codex MCP.

Related Skills

Explore More Software Engineering Skills→
leejaedusleejaedus

analyze

Analyze architecture, bugs, performance issues, and dependencies to identify root causes.

Community
Intermediate
devstefanchodevstefancho
11

code-quality-reviewer

Identify and remediate code quality issues using DRY, KISS, and CLEAN CODE principles.

Community
Advanced
realsigridjinrealsigridjin
20

analyze

Investigate software bug root causes with evidence-based findings.

Community
Advanced
lidge-junlidge-jun
5

semgrep

Execute Semgrep static analysis scans to detect vulnerabilities and code quality issues.

Community
Advanced