Comprehensive Review Full Review

1---
2name: comprehensive-review-full-review
3description: "Use when working with comprehensive review full review"
4---
5 
6## Use this skill when
7 
8- Working on comprehensive review full review tasks or workflows
9- Needing guidance, best practices, or checklists for comprehensive review full review
10 
11## Do not use this skill when
12 
13- The task is unrelated to comprehensive review full review
14- You need a different domain or tool outside this scope
15 
16## Instructions
17 
18- Clarify goals, constraints, and required inputs.
19- Apply relevant best practices and validate outcomes.
20- Provide actionable steps and verification.
21- If detailed examples are required, open `resources/implementation-playbook.md`.
22 
23Orchestrate comprehensive multi-dimensional code review using specialized review agents
24 
25[Extended thinking: This workflow performs an exhaustive code review by orchestrating multiple specialized agents in sequential phases. Each phase builds upon previous findings to create a comprehensive review that covers code quality, security, performance, testing, documentation, and best practices. The workflow integrates modern AI-assisted review tools, static analysis, security scanning, and automated quality metrics. Results are consolidated into actionable feedback with clear prioritization and remediation guidance. The phased approach ensures thorough coverage while maintaining efficiency through parallel agent execution where appropriate.]
26 
27## Review Configuration Options
28 
29- **--security-focus**: Prioritize security vulnerabilities and OWASP compliance
30- **--performance-critical**: Emphasize performance bottlenecks and scalability issues
31- **--tdd-review**: Include TDD compliance and test-first verification
32- **--ai-assisted**: Enable AI-powered review tools (Copilot, Codium, Bito)
33- **--strict-mode**: Fail review on any critical issues found
34- **--metrics-report**: Generate detailed quality metrics dashboard
35- **--framework [name]**: Apply framework-specific best practices (React, Spring, Django, etc.)
36 
37## Phase 1: Code Quality & Architecture Review
38 
39Use Task tool to orchestrate quality and architecture agents in parallel:
40 
41### 1A. Code Quality Analysis
42- Use Task tool with subagent_type="code-reviewer"
43- Prompt: "Perform comprehensive code quality review for: $ARGUMENTS. Analyze code complexity, maintainability index, technical debt, code duplication, naming conventions, and adherence to Clean Code principles. Integrate with SonarQube, CodeQL, and Semgrep for static analysis. Check for code smells, anti-patterns, and violations of SOLID principles. Generate cyclomatic complexity metrics and identify refactoring opportunities."
44- Expected output: Quality metrics, code smell inventory, refactoring recommendations
45- Context: Initial codebase analysis, no dependencies on other phases
46 
47### 1B. Architecture & Design Review
48- Use Task tool with subagent_type="architect-review"
49- Prompt: "Review architectural design patterns and structural integrity in: $ARGUMENTS. Evaluate microservices boundaries, API design, database schema, dependency management, and adherence to Domain-Driven Design principles. Check for circular dependencies, inappropriate coupling, missing abstractions, and architectural drift. Verify compliance with enterprise architecture standards and cloud-native patterns."
50- Expected output: Architecture assessment, design pattern analysis, structural recommendations
51- Context: Runs parallel with code quality analysis
52 
53## Phase 2: Security & Performance Review
54 
55Use Task tool with security and performance agents, incorporating Phase 1 findings:
56 
57### 2A. Security Vulnerability Assessment
58- Use Task tool with subagent_type="security-auditor"
59- Prompt: "Execute comprehensive security audit on: $ARGUMENTS. Perform OWASP Top 10 analysis, dependency vulnerability scanning with Snyk/Trivy, secrets detection with GitLeaks, input validation review, authentication/authorization assessment, and cryptographic implementation review. Include findings from Phase 1 architecture review: {phase1_architecture_context}. Check for SQL injection, XSS, CSRF, insecure deserialization, and configuration security issues."
60- Expected output: Vulnerability report, CVE list, security risk matrix, remediation steps
61- Context: Incorporates architectural vulnerabilities identified in Phase 1B
62 
63### 2B. Performance & Scalability Analysis
64- Use Task tool with subagent_type="application-performance::performance-engineer"
65- Prompt: "Conduct performance analysis and scalability assessment for: $ARGUMENTS. Profile code for CPU/memory hotspots, analyze database query performance, review caching strategies, identify N+1 problems, assess connection pooling, and evaluate asynchronous processing patterns. Consider architectural findings from Phase 1: {phase1_architecture_context}. Check for memory leaks, resource contention, and bottlenecks under load."
66- Expected output: Performance metrics, bottleneck analysis, optimization recommendations
67- Context: Uses architecture insights to identify systemic performance issues
68 
69## Phase 3: Testing & Documentation Review
70 
71Use Task tool for test and documentation quality assessment:
72 
73### 3A. Test Coverage & Quality Analysis
74- Use Task tool with subagent_type="unit-testing::test-automator"
75- Prompt: "Evaluate testing strategy and implementation for: $ARGUMENTS. Analyze unit test coverage, integration test completeness, end-to-end test scenarios, test pyramid adherence, and test maintainability. Review test quality metrics including assertion density, test isolation, mock usage, and flakiness. Consider security and performance test requirements from Phase 2: {phase2_security_context}, {phase2_performance_context}. Verify TDD practices if --tdd-review flag is set."
76- Expected output: Coverage report, test quality metrics, testing gap analysis
77- Context: Incorporates security and performance testing requirements from Phase 2
78 
79### 3B. Documentation & API Specification Review
80- Use Task tool with subagent_type="code-documentation::docs-architect"
81- Prompt: "Review documentation completeness and quality for: $ARGUMENTS. Assess inline code documentation, API documentation (OpenAPI/Swagger), architecture decision records (ADRs), README completeness, deployment guides, and runbooks. Verify documentation reflects actual implementation based on all previous phase findings: {phase1_context}, {phase2_context}. Check for outdated documentation, missing examples, and unclear explanations."
82- Expected output: Documentation coverage report, inconsistency list, improvement recommendations
83- Context: Cross-references all previous findings to ensure documentation accuracy
84 
85## Phase 4: Best Practices & Standards Compliance
86 
87Use Task tool to verify framework-specific and industry best practices:
88 
89### 4A. Framework & Language Best Practices
90- Use Task tool with subagent_type="framework-migration::legacy-modernizer"
91- Prompt: "Verify adherence to framework and language best practices for: $ARGUMENTS. Check modern JavaScript/TypeScript patterns, React hooks best practices, Python PEP compliance, Java enterprise patterns, Go idiomatic code, or framework-specific conventions (based on --framework flag). Review package management, build configuration, environment handling, and deployment practices. Include all quality issues from previous phases: {all_previous_contexts}."
92- Expected output: Best practices compliance report, modernization recommendations
93- Context: Synthesizes all previous findings for framework-specific guidance
94 
95### 4B. CI/CD & DevOps Practices Review
96- Use Task tool with subagent_type="cicd-automation::deployment-engineer"
97- Prompt: "Review CI/CD pipeline and DevOps practices for: $ARGUMENTS. Evaluate build automation, test automation integration, deployment strategies (blue-green, canary), infrastructure as code, monitoring/observability setup, and incident response procedures. Assess pipeline security, artifact management, and rollback capabilities. Consider all issues identified in previous phases that impact deployment: {all_critical_issues}."
98- Expected output: Pipeline assessment, DevOps maturity evaluation, automation recommendations
99- Context: Focuses on operationalizing fixes for all identified issues
100 
101## Consolidated Report Generation
102 
103Compile all phase outputs into comprehensive review report:
104 
105### Critical Issues (P0 - Must Fix Immediately)
106- Security vulnerabilities with CVSS > 7.0
107- Data loss or corruption risks
108- Authentication/authorization bypasses
109- Production stability threats
110- Compliance violations (GDPR, PCI DSS, SOC2)
111 
112### High Priority (P1 - Fix Before Next Release)
113- Performance bottlenecks impacting user experience
114- Missing critical test coverage
115- Architectural anti-patterns causing technical debt
116- Outdated dependencies with known vulnerabilities
117- Code quality issues affecting maintainability
118 
119### Medium Priority (P2 - Plan for Next Sprint)
120- Non-critical performance optimizations
121- Documentation gaps and inconsistencies
122- Code refactoring opportunities
123- Test quality improvements
124- DevOps automation enhancements
125 
126### Low Priority (P3 - Track in Backlog)
127- Style guide violations
128- Minor code smell issues
129- Nice-to-have documentation updates
130- Cosmetic improvements
131 
132## Success Criteria
133 
134Review is considered successful when:
135- All critical security vulnerabilities are identified and documented
136- Performance bottlenecks are profiled with remediation paths
137- Test coverage gaps are mapped with priority recommendations
138- Architecture risks are assessed with mitigation strategies
139- Documentation reflects actual implementation state
140- Framework best practices compliance is verified
141- CI/CD pipeline supports safe deployment of reviewed code
142- Clear, actionable feedback is provided for all findings
143- Metrics dashboard shows improvement trends
144- Team has clear prioritized action plan for remediation
145 
146Target: $ARGUMENTS
147