Deep Analysis Skill

Comprehensive analytical templates for thorough investigation, audits, and evaluations leveraging extended thinking capabilities.

When to Use

• Code audits requiring systematic review

• Security assessments and threat modeling

• Performance analysis and optimization planning

• Architecture reviews and technical debt assessment

• Incident post-mortems and root cause analysis

• Compliance audits and risk assessments

Analysis Templates

Code Audit Template

Code Audit Report

Repository: [repo-name] Scope: [files/modules audited] Date: [YYYY-MM-DD] Auditor: Claude + [Human reviewer]

Executive Summary

[2-3 sentence overview of findings]

Audit Criteria

• Code quality and maintainability
• Security vulnerabilities
• Performance concerns
• Test coverage
• Documentation completeness
• Dependency health

Critical Findings

High Priority Findings

Medium Priority Findings

[...]

Low Priority / Suggestions

[...]

Metrics

Recommendations

1. Immediate: [Critical fixes]
2. Short-term: [Within sprint]
3. Long-term: [Tech debt reduction]

Sign-off

• All critical issues addressed
• High priority issues have timeline
• Audit findings documented in backlog

Security Threat Model Template

Threat Model: [System/Component Name]

Version: [1.0] Last Updated: [YYYY-MM-DD] Classification: [Internal/Confidential]

System Overview

[Brief description of the system being modeled]

Assets

Trust Boundaries

┌─────────────────────────────────────────┐ │ External (Untrusted) │ │ [Internet Users] [Third-party APIs] │ └──────────────────┬──────────────────────┘ │ WAF/Load Balancer ┌──────────────────┴──────────────────────┐ │ DMZ (Semi-trusted) │ │ [API Gateway] [CDN] [Public Services] │ └──────────────────┬──────────────────────┘ │ Internal Firewall ┌──────────────────┴──────────────────────┐ │ Internal (Trusted) │ │ [App Servers] [Databases] [Queues] │ └─────────────────────────────────────────┘

Threat Categories (STRIDE)

Spoofing

Tampering

Repudiation

[...]

Information Disclosure

[...]

Denial of Service

[...]

Elevation of Privilege

[...]

Attack Vectors

1. Vector 1: [Description]
   • Entry point: [Where]
   • Technique: [How]
   • Mitigation: [Defense]

Risk Matrix

Security Controls

Recommendations

1. [Priority 1 recommendations]
2. [Priority 2 recommendations]
3. [Priority 3 recommendations]

Performance Analysis Template

Performance Analysis Report

System: [System name] Period: [Date range] Environment: [Production/Staging]

Executive Summary

[Key findings and recommendations]

Performance Metrics

Response Times

Throughput

Resource Utilization

Bottleneck Analysis

Identified Bottlenecks

1. Database Queries (High Impact)

   • Location: /api/search endpoint
   • Cause: Missing index on created_at column
   • Impact: 890ms P95 latency
   • Fix: Add composite index

2. Memory Pressure (Medium Impact)

   • Location: Report generation service
   • Cause: Large dataset loading into memory
   • Impact: GC pauses, OOM risks
   • Fix: Implement streaming/pagination

Load Test Results

Optimization Recommendations

Quick Wins (This Sprint)

1. Add database indexes - Expected: 40% improvement
2. Enable query caching - Expected: 25% improvement
3. Optimize N+1 queries - Expected: 30% improvement

Medium Term (Next Quarter)

1. Implement read replicas
2. Add CDN for static assets
3. Optimize serialization

Long Term (6+ Months)

1. Service decomposition
2. Event-driven architecture
3. Edge computing deployment

Capacity Planning

Architecture Review Template

Architecture Review

System: [System name] Version: [Current architecture version] Review Date: [YYYY-MM-DD] Participants: [Team members]

Current Architecture

System Diagram

[Include architecture diagram or ASCII representation]

Components

Data Flow

1. User request → API Gateway
2. API Gateway → Auth validation
3. Auth → Core API
4. Core API → Database
5. Response → User

Evaluation Criteria

Scalability

Reliability

Maintainability

Technical Debt Assessment

Recommendations

Immediate (0-3 months)

1. [Recommendation 1]
2. [Recommendation 2]

Short-term (3-6 months)

1. [Recommendation 1]
2. [Recommendation 2]

Long-term (6-12 months)

1. [Recommendation 1]
2. [Recommendation 2]

Decision Log

Integration with Extended Thinking

For deep analysis tasks, use maximum thinking budget:

response = client.messages.create( model="claude-opus-4-5-20250514", max_tokens=32000, thinking={ "type": "enabled", "budget_tokens": 25000 # Maximum budget for deep analysis }, system="""You are a senior technical analyst performing a comprehensive review. Use structured analysis templates and document all findings systematically.""", messages=[{ "role": "user", "content": "Perform a security threat model for..." }] )

Best Practices

• Use appropriate templates: Match template to analysis type

• Be systematic: Follow the template structure completely

• Quantify findings: Use metrics and severity ratings

• Prioritize actionable: Focus on findings that can be fixed

• Document evidence: Link to specific code/logs/data

• Track progress: Update findings as they're addressed

See Also

• [[extended-thinking]] - Enable deep reasoning capabilities

• [[complex-reasoning]] - Reasoning frameworks

• [[testing]] - Validation strategies

• [[debugging]] - Issue investigation