analyze
Run read-only deep repository analysis and return a ranked synthesis with explicit confidence, concrete file references, and clear evidence-vs-inference boundaries. Use when a user says 'analyze', 'investigate', 'why does', 'what's causing', or needs grounded cross-file explanation before any changes are proposed.
Best for Pre-change impact analysisWorks with GitHubLow risk
⌘source
- author
@Yeachan-Heo- language
- TypeScript
★24kstars
2kforks
Apr 19, 2026
✦overview.md
Key Features
- ·Read-only repository analysis
- ·Ranked synthesis with confidence levels
- ·Concrete file references
- ·Clear evidence-vs-inference boundaries
- ·Cross-file behavior tracing
- ·Architecture and causality explanations
Use Cases
- →Understanding why a workflow behaves a certain way
- →Tracing how a feature is wired across modules
- →Investigating likely causes of failures or regressions
- →Assessing impact of changing dependencies or contracts
- →Determining best-supported interpretation of codebase
Best for
- ✓Pre-change impact analysis
- ✓Cross-module investigation
- ✓Root cause analysis
Not ideal for
- !Code editing requests
- !Implementation tasks
- !Execution or fixes
FAQs
name
analyze
description
Run read-only deep repository analysis and return a ranked synthesis with explicit confidence, concrete file references, and clear evidence-vs-inference boundaries. Use when a user says 'analyze', 'investigate', 'why does', 'what's causing', or needs grounded cross-file explanation before any changes are proposed.
Analyze — Read-Only Deep Analysis
Use this skill to answer the user’s question through read-only repository analysis. The goal is to explain what the codebase most likely says about the question, not to drift into implementation, debugging theater, or generic fix planning.
Use $analyze when
- the user wants a grounded explanation, not code changes
- the answer requires reading multiple files or tracing behavior across boundaries
- there are several plausible explanations and they need to be ranked
- confidence should reflect the strength of the available evidence
- the user wants to understand architecture, behavior, causality, impact, or tradeoffs before changing anything
Examples:
- why a workflow behaves a certain way
- how a feature is wired across modules
- what likely explains a failure, regression, or mismatch
- what would be impacted by changing a dependency or contract
- which interpretation of the current codebase is best supported
Do not use $analyze when
- the user explicitly wants code edits, a fix, or execution — use the appropriate implementation lane instead
- the user wants a new product plan or acceptance criteria — use
$plan/$ralplan
$install
1-click copynpx skills add Yeachan-Heo/oh-my-codex --skill analyzeSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
5/ 5
excellentVery clear and well structured, with almost no room for misunderstanding.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
5/ 5
very highHighly actionable with clear, concrete steps that an agent can follow directly.