analyze

Deep analysis and investigation

11 stars

byMeroZemory

View on GitHub Installation ↓

Best use case

analyze is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Deep analysis and investigation

Teams using analyze should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/analyze/SKILL.md --create-dirs "https://raw.githubusercontent.com/MeroZemory/oh-my-droid/main/skills/analyze/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/analyze/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How analyze Compares

Feature / Agent	analyze	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

Deep analysis and investigation

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Deep Analysis Mode

[ANALYSIS MODE ACTIVATED]

## Objective

Conduct thorough analysis of the specified target (code, architecture, issue, bug, performance bottleneck, security concern).

## Approach

1. **Gather Context**
   - Read relevant files
   - Check git history if relevant
   - Review related issues/PRs if applicable

2. **Analyze Systematically**
   - Identify patterns and antipatterns
   - Trace execution flows
   - Map dependencies and relationships
   - Check for edge cases

   **For Debugging/Bug Analysis (4-Phase Protocol)**

   When analyzing bugs or issues, follow systematic debugging:

   - **Root Cause First** - Never skip to fixes
     - Read ALL error messages
     - Reproduce consistently
     - Document hypothesis before looking at code

   - **Pattern Analysis** - Find working vs broken
     - Compare with working similar code
     - Identify the specific delta

   - **3-Failure Circuit Breaker** - If stuck:
     - After 3 failed hypotheses, question the architecture
     - The bug may be elsewhere entirely

3. **Synthesize Findings**
   - Root cause (for bugs)
   - Design decisions and tradeoffs (for architecture)
   - Bottlenecks and hotspots (for performance)
   - Vulnerabilities and risks (for security)

4. **Provide Recommendations**
   - Concrete, actionable next steps
   - Prioritized by impact
   - Consider maintainability and technical debt

## Output Format

Present findings clearly:
- **Summary** (2-3 sentences)
- **Key Findings** (bulleted list)
- **Analysis** (detailed explanation)
- **Recommendations** (prioritized)

Stay objective. Cite file paths and line numbers. No speculation without evidence.

Related Skills

We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.