UNPKG

@endgame-build/claude-workflows

Version:

Claude Code workflow system with commands, agents, and templates for AI-native development

107 lines (80 loc) 2.47 kB
# Code Analysis Report: {PROJECT/COMPONENT} **Date**: {DATE} **Scope**: {SCOPE_DESCRIPTION} **Type**: {General/Architecture/Performance/Security/Quality} ## Executive Summary {High-level findings in 2-3 sentences} ## Analysis Overview ### Metrics - **Files Analyzed**: {X} - **Lines of Code**: {X} - **Complexity Score**: {X}/10 - **Technical Debt**: {Low/Medium/High} ## Key Findings ### 🟢 Strengths 1. **{Strength Category}** - {Specific positive finding} - {Evidence/example} 2. **{Strength Category}** - {Specific positive finding} - {Evidence/example} ### 🟡 Areas for Improvement 1. **{Improvement Category}** - **Current**: {Current state} - **Recommended**: {Desired state} - **Impact**: {Why it matters} - **Effort**: {XS/S/M/L/XL} 2. **{Improvement Category}** - **Current**: {Current state} - **Recommended**: {Desired state} - **Impact**: {Why it matters} - **Effort**: {XS/S/M/L/XL} ### 🔴 Critical Issues 1. **{Issue Category}** - **Severity**: {Critical/High/Medium/Low} - **Description**: {What's wrong} - **Risk**: {What could happen} - **Resolution**: {How to fix} ## Detailed Analysis ### Architecture Assessment - **Pattern Consistency**: {Assessment} - **Separation of Concerns**: {Assessment} - **Scalability**: {Assessment} - **Maintainability**: {Assessment} ### Code Quality - **Readability**: {Score}/10 - **Duplication**: {X}% detected - **Complexity**: {Average cyclomatic complexity} - **Test Coverage**: {X}% ### Performance Considerations - **Bottlenecks**: {Identified bottlenecks} - **Optimization Opportunities**: {List} - **Resource Usage**: {Assessment} ### Security Review - **Vulnerabilities Found**: {Count and types} - **Authentication**: {Assessment} - **Data Protection**: {Assessment} - **Input Validation**: {Assessment} ## Recommendations ### Immediate Actions (High Priority) 1. {Critical fix that should be done now} 2. {Security issue that needs addressing} ### Short-term Improvements (1-2 weeks) 1. {Refactoring opportunity} 2. {Performance optimization} ### Long-term Enhancements (1-3 months) 1. {Architectural improvement} 2. {Major refactoring} ## Implementation Roadmap ``` Week 1-2: Critical Fixes {Specific tasks} Week 3-4: Quick Wins {Specific tasks} Month 2: Refactoring {Specific tasks} Month 3: Architecture {Specific tasks} ``` ## Conclusion {Summary of analysis and recommended next steps}