Investigate software bug root causes with evidence-based findings.
npx skills add https://github.com/realsigridjin/oh-my-codex --skill analyze-realsigridjin
Please help me install this Agent Skill. Skill: analyze Source: https://github.com/realsigridjin/oh-my-codex/tree/main/skills/analyze Command: npx skills add https://github.com/realsigridjin/oh-my-codex --skill analyze-realsigridjin
This Skill helps uncover the causes of complex bugs, performance issues, dependency problems, and architectural questions without stopping at surface-level observations.
Use the analyze skill to investigate why the WebSocket connections in this project drop after 30 seconds.
High-intent search queries and answers about installing and using this skill.
To investigate cross-file architectural behavior, you provide relevant context files for broad context gathering. The analysis routes through Codex MCP with an architect role or an architect agent fallback to evaluate dependencies and structural impacts.
The best way to debug performance issues and dependency impacts is through structured investigation that examines architecture and behavior. This Skill uncovers causes beyond surface-level observations by returning grounded, evidence-based findings with actionable recommendations.
Yes, relevant context files are required to perform root cause analysis. The investigation requires these files to gather broad context, apply evidence-based reasoning across multiple files, and generate structured findings with specific file references.
Architecture analysis works by routing provided context files through Codex MCP with an architect role or an architect agent fallback. This mechanism applies evidence-based reasoning to evaluate architectural behavior, dependency impacts, and performance concerns across multiple files.
Yes, you can investigate why WebSocket connections drop unexpectedly by gathering relevant source files and requesting a grounded root-cause analysis. The investigation examines cross-file behavior and architecture to return structured conclusions and hypotheses.
KYRIE66nbAnalyze codebases for architecture, bug, and performance issues with evidence-backed root-cause findings.
allcllAnalyze backend code and system behavior to identify root causes and risks.
shaun0927Analyze codebase architecture, bugs, performance, and dependencies with structured findings.
leejaedusAnalyze architecture, bugs, performance issues, and dependencies to identify root causes.
