Can this skill help with performance optimization?

Yes, it is designed to identify bottlenecks and hotspots by tracing execution flows and analyzing system patterns.

How does the analyze skill differ from standard Claude debugging?

Unlike standard responses, the analyze skill follows a strict 4-phase protocol that mandates root-cause identification and evidence gathering before suggesting any code changes.

What is the '3-Failure Circuit Breaker'?

It is a logical safeguard that forces the AI to question the underlying architecture or look elsewhere entirely if three consecutive hypotheses fail to explain a bug.

Does it provide specific code references?

Yes, the skill is configured to remain objective and cite specific file paths and line numbers for all findings.

Deep Code Analysis

Name: Deep Code Analysis
Author: Yeachan-Heo

byYeachan-Heo

•

2,142

보안 및 테스팅

Conducts systematic investigations and root-cause analysis to solve complex bugs and architectural issues.

소개

The Deep Code Analysis skill empowers Claude to perform rigorous, evidence-based investigations into software systems. It utilizes a specialized 4-phase debugging protocol that prioritizes root-cause identification over quick fixes, preventing technical debt. By mapping dependencies, tracing execution flows, and employing a '3-failure circuit breaker' to re-evaluate stuck problems, this skill provides objective insights into performance bottlenecks, security risks, and architectural tradeoffs, resulting in actionable recommendations backed by specific code evidence.

주요 기능

4-Phase Debugging Protocol for systematic root cause identification
3-Failure Circuit Breaker to prevent circular logic during troubleshooting
Evidence-based reporting with specific file path and line number citations
Comprehensive architectural mapping and dependency relationship tracing
Performance bottleneck and security vulnerability detection
2,142 GitHub stars

사용 사례

Profiling performance hotspots and mapping system-wide dependencies
Identifying the root cause of intermittent or complex 'heisenbugs'
Conducting security and architectural audits for new feature implementations

소개

주요 기능

4-Phase Debugging Protocol for systematic root cause identification
3-Failure Circuit Breaker to prevent circular logic during troubleshooting
Evidence-based reporting with specific file path and line number citations
Comprehensive architectural mapping and dependency relationship tracing
Performance bottleneck and security vulnerability detection
2,142 GitHub stars

사용 사례

Profiling performance hotspots and mapping system-wide dependencies
Identifying the root cause of intermittent or complex 'heisenbugs'
Conducting security and architectural audits for new feature implementations