Skill

analyze

Conducts systematic deep analysis of code, bugs, architecture, performance, and security issues. Follows 4-phase debugging protocol with root cause focus and structured output of findings and recommendations.

code-quality

performance

security

npx claudepluginhub mazenyassergithub/oh-my-claudecode --plugin oh-my-claudecode

Tool Access

This skill uses the workspace's default tool permissions.

Preview

[ANALYSIS MODE ACTIVATED]

SKILL.md

Similar Skills

cache-components

139.2k

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

canvas-design

124.2k

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

20 files

anthropics-skills-13

Stats

Stars5

Forks0

Last CommitJan 22, 2026

Used By2 plugins

Actions

View Source View Plugin View on GitHub View README

Deep Analysis Mode

[ANALYSIS MODE ACTIVATED]

Objective

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

Approach

Gather Context
- Read relevant files
- Check git history if relevant
- Review related issues/PRs if applicable
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
Synthesize Findings
- Root cause (for bugs)
- Design decisions and tradeoffs (for architecture)
- Bottlenecks and hotspots (for performance)
- Vulnerabilities and risks (for security)
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.