UNPKG

@endgame-build/claude-workflows

Version:

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

110 lines (83 loc) 3.82 kB
# Code Review Summary Template Use this template to present code review findings consistently across review commands. ## Review Findings ### Critical Issues (Must Fix) [List each issue with file:line references and explanation] - **[Issue Type]**: [Description] (`file:line`) - Why: [Explanation of the risk/problem] - Fix: [Suggested solution] ### Major Concerns (Should Fix) [List significant issues that should be addressed] - **[Concern Type]**: [Description] (`file:line`) - Impact: [Potential consequences] - Suggestion: [Recommended approach] ### Minor Suggestions (Consider) [List improvements that would enhance code quality] - **[Category]**: [Description] (`file:line`) - Benefit: [Why this would help] ## Compliance Analysis ### Security Analysis - **Authentication**: ✅/❌ [Details of auth implementation] - **Authorization**: ✅/❌ [Access control assessment] - **Input Validation**: ✅/❌ [Data sanitization status] - **Security Best Practices**: ✅/❌ [Following security standards] - **Secrets Management**: ✅/❌ [No hardcoded secrets] ### Architecture Compliance - **Separation of Concerns**: ✅/❌ [Clear layer boundaries] - **Service Isolation**: ✅/❌ [Proper service boundaries] - **Design Patterns**: ✅/❌ [Appropriate pattern usage] - **Environment Support**: ✅/❌ [Platform compatibility] - **Dependencies**: ✅/❌ [Proper dependency management] ### Code Standards Compliance - **Language Conventions**: ✅/❌ [Following language idioms] - **Import/Export Style**: ✅/❌ [Module system compliance] - **Naming Conventions**: ✅/❌ [Consistent naming] - **Code Organization**: ✅/❌ [Logical file structure] - **Error Handling**: ✅/❌ [Consistent error patterns] ### Type Safety Analysis - **Type System Usage**: ✅/❌ [Proper type definitions and usage] - **Type Flow Integrity**: ✅/❌ [Types consistent throughout] - **Validation Compliance**: ✅/❌ [Input/output validation] - **Contract Adherence**: ✅/❌ [API contracts respected] - **Type Safety**: ✅/❌ [No unsafe type operations] ### Performance Analysis - **Algorithm Efficiency**: [Complexity analysis] - **Resource Usage**: [Memory/CPU considerations] - **Scalability**: [Performance under load] - **Optimization**: [Caching, batching status] ### Implementation Quality Analysis - **Async Safety**: ✅/❌ [Proper async/await patterns] - **State Management**: ✅/❌ [Clean state handling] - **Configuration**: ✅/❌ [Externalized configuration] - **Error Propagation**: ✅/❌ [Consistent error handling] - **API Compliance**: ✅/❌ [Response format consistency] ### Resource Management Analysis - **Connection Handling**: ✅/❌ [Resources properly released] - **Memory Management**: ✅/❌ [No memory leaks] - **Cleanup Logic**: ✅/❌ [Proper cleanup on errors] - **Transaction Scope**: ✅/❌ [Atomic operations] - **Resource Limits**: ✅/❌ [Bounded resource usage] ### Testing Analysis - **Test Coverage**: ✅/❌ [Critical paths tested] - **Test Quality**: ✅/❌ [Meaningful test cases] - **Edge Cases**: ✅/❌ [Boundary conditions tested] - **Error Scenarios**: ✅/❌ [Failure cases tested] - **Integration Tests**: ✅/❌ [System integration verified] ## Overall Assessment ### Compliance Score: X/10 - Security: X/10 - Architecture: X/10 - Code Quality: X/10 - Performance: X/10 - Testing: X/10 ### Risk Level: [Low/Medium/High] [Explanation of risk assessment based on findings] ### Action Items - [ ] Address all critical issues before merge - [ ] Fix major concerns identified - [ ] Ensure all tests pass - [ ] Update documentation if needed - [ ] Verify no breaking changes or document them ### Recommendation [✅ Approve / ⚠️ Approve with changes / ❌ Request changes] [Brief explanation of the recommendation]