Purpose
Provide comprehensive project health analysis covering structural integrity, security posture, performance characteristics, and overall code stability. This skill leverages the codebase-analyzer agent along with specialized sub-agents to deliver a thorough quality assessment.
When to Use
Use this skill when you need to:
- Audit project health - Get a complete quality assessment of the codebase
- Identify structural issues - Find architectural problems and anti-patterns
- Security review - Detect potential vulnerabilities and security concerns
- Performance analysis - Identify performance bottlenecks and inefficiencies
- Code stability check - Assess test coverage, error handling, and reliability
- Pre-release review - Validate codebase before major releases
- Technical debt assessment - Quantify and prioritize technical debt
Analysis Categories
1. Structural Analysis
Evaluate the overall architecture and organization:
Directory Structure
- Consistency - Naming conventions, folder organization
- Separation of Concerns - Clear boundaries between layers
- Module Boundaries - Proper encapsulation and dependencies
- Dead Code - Unused files, orphaned modules
Architecture Patterns
- Pattern Consistency - Adherence to chosen patterns (MVC, Clean Architecture, etc.)
- Dependency Direction - Proper dependency flow (inner layers don't depend on outer)
- Circular Dependencies - Identify and report cycles
- Coupling Analysis - Measure inter-module dependencies
Code Organization
- File Size - Identify overly large files (>500 lines)
- Function Complexity - Cyclomatic complexity analysis
- Naming Conventions - Consistency in naming
- Code Duplication - Detect copy-paste patterns
2. Security Analysis
Identify potential security vulnerabilities:
OWASP Top 10 Checks
- Injection Flaws - SQL, NoSQL, OS command injection patterns
- Broken Authentication - Weak auth patterns, hardcoded credentials
- Sensitive Data Exposure - Unencrypted secrets, logging PII
- XML External Entities (XXE) - Unsafe XML parsing
- Broken Access Control - Missing authorization checks
- Security Misconfiguration - Debug modes, default configs
- XSS - Unsanitized user input in output
- Insecure Deserialization - Unsafe object serialization
- Vulnerable Dependencies - Known CVEs in dependencies
- Insufficient Logging - Missing audit trails
Code-Level Security
- Secret Management - Hardcoded API keys, passwords
- Input Validation - Missing or weak validation
- Output Encoding - Proper escaping for context
- Error Handling - Information leakage in errors
- Cryptography - Weak algorithms, improper usage
3. Performance Analysis
Identify performance concerns:
Code Efficiency
- Algorithm Complexity - O(n²) or worse patterns
- Memory Leaks - Unclosed resources, unbounded caches
- N+1 Queries - Database query patterns
- Unnecessary Operations - Redundant computations
Resource Management
- Connection Pooling - Database, HTTP connections
- Caching Strategy - Missing or ineffective caching
- Async Operations - Blocking calls in async contexts
- Bundle Size - Large dependencies, unused imports (frontend)
Scalability Concerns
- State Management - Stateful components that prevent scaling
- Race Conditions - Concurrent access patterns
- Resource Limits - Hardcoded limits, unbounded growth
4. Code Stability
Assess reliability and maintainability:
Test Coverage
- Unit Tests - Coverage percentage, critical path coverage
- Integration Tests - API and service integration testing
- E2E Tests - User journey coverage
- Test Quality - Assertions, edge cases, mocking patterns
Error Handling
- Exception Coverage - Unhandled exceptions
- Graceful Degradation - Fallback mechanisms
- Recovery Patterns - Retry logic, circuit breakers
- Error Reporting - Proper error classification and logging
Code Quality
- Type Safety - TypeScript strict mode, type coverage
- Null Safety - Null/undefined handling
- Documentation - Critical function documentation
- TODO/FIXME - Outstanding technical debt markers
Health Score Calculation
Generate a health score (0-100) based on weighted categories:
| Category |
Weight |
Metrics |
| Structure |
25% |
Architecture consistency, code organization, complexity |
| Security |
30% |
Vulnerability count, secret exposure, dependency health |
| Performance |
20% |
Efficiency patterns, resource management |
| Stability |
25% |
Test coverage, error handling, type safety |
Scoring Rubric
Structure (25 points)
- 25: Clean architecture, consistent patterns, low complexity
- 20: Minor inconsistencies, acceptable complexity
- 15: Some architectural issues, moderate complexity
- 10: Significant structural problems
- 5: Major architectural issues, high complexity
Security (30 points)
- 30: No vulnerabilities, proper secret management, secure patterns
- 24: Minor security concerns, no critical issues
- 18: Some vulnerabilities, needs attention
- 12: Multiple security issues
- 6: Critical security vulnerabilities
Performance (20 points)
- 20: Efficient code, proper resource management
- 16: Minor inefficiencies
- 12: Some performance concerns
- 8: Significant performance issues
- 4: Major performance problems
Stability (25 points)
- 25: High test coverage (>80%), comprehensive error handling
- 20: Good coverage (60-80%), adequate error handling
- 15: Moderate coverage (40-60%), basic error handling
- 10: Low coverage (20-40%), minimal error handling
- 5: Very low coverage (<20%), poor error handling
Output Format
Generate a comprehensive health report:
# Project Health Report
## Summary
- **Overall Health Score**: XX/100
- **Risk Level**: Low/Medium/High/Critical
- **Assessment Date**: YYYY-MM-DD
## Category Scores
| Category | Score | Status |
|----------|-------|--------|
| Structure | XX/25 | 🟢/🟡/🔴 |
| Security | XX/30 | 🟢/🟡/🔴 |
| Performance | XX/20 | 🟢/🟡/🔴 |
| Stability | XX/25 | 🟢/🟡/🔴 |
## Critical Issues (Immediate Action Required)
1. [Issue description with file:line reference]
2. ...
## High Priority Issues
1. [Issue description]
2. ...
## Medium Priority Issues
1. [Issue description]
2. ...
## Recommendations
1. [Actionable recommendation]
2. ...
## Detailed Findings
### Structure Analysis
[Detailed findings]
### Security Analysis
[Detailed findings]
### Performance Analysis
[Detailed findings]
### Stability Analysis
[Detailed findings]
Integration with CI/CD
This skill can be used to:
- Generate reports for code review
- Block PRs with critical issues
- Track health metrics over time
- Set quality gates for releases
Related Skills
analyze-codebase - Deep architectural analysis
security-audit - Detailed security review
performance-review - Performance profiling
test-coverage - Test coverage analysis
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: review-project3description: Analyze project health including structural issues, security vulnerabilities, performance concerns, and code stability metrics. Use when auditing codebases, reviewing project quality, checking for security issues, identifying architectural problems, measuring code health, or generating quality reports. Use when this capability is needed.4---56## Purpose78Provide comprehensive project health analysis covering structural integrity, security posture, performance characteristics, and overall code stability. This skill leverages the codebase-analyzer agent along with specialized sub-agents to deliver a thorough quality assessment.910## When to Use1112Use this skill when you need to:1314- **Audit project health** - Get a complete quality assessment of the codebase15- **Identify structural issues** - Find architectural problems and anti-patterns16- **Security review** - Detect potential vulnerabilities and security concerns17- **Performance analysis** - Identify performance bottlenecks and inefficiencies18- **Code stability check** - Assess test coverage, error handling, and reliability19- **Pre-release review** - Validate codebase before major releases20- **Technical debt assessment** - Quantify and prioritize technical debt2122## Analysis Categories2324### 1. Structural Analysis2526Evaluate the overall architecture and organization:2728#### Directory Structure29- **Consistency** - Naming conventions, folder organization30- **Separation of Concerns** - Clear boundaries between layers31- **Module Boundaries** - Proper encapsulation and dependencies32- **Dead Code** - Unused files, orphaned modules3334#### Architecture Patterns35- **Pattern Consistency** - Adherence to chosen patterns (MVC, Clean Architecture, etc.)36- **Dependency Direction** - Proper dependency flow (inner layers don't depend on outer)37- **Circular Dependencies** - Identify and report cycles38- **Coupling Analysis** - Measure inter-module dependencies3940#### Code Organization41- **File Size** - Identify overly large files (>500 lines)42- **Function Complexity** - Cyclomatic complexity analysis43- **Naming Conventions** - Consistency in naming44- **Code Duplication** - Detect copy-paste patterns4546### 2. Security Analysis4748Identify potential security vulnerabilities:4950#### OWASP Top 10 Checks51- **Injection Flaws** - SQL, NoSQL, OS command injection patterns52- **Broken Authentication** - Weak auth patterns, hardcoded credentials53- **Sensitive Data Exposure** - Unencrypted secrets, logging PII54- **XML External Entities (XXE)** - Unsafe XML parsing55- **Broken Access Control** - Missing authorization checks56- **Security Misconfiguration** - Debug modes, default configs57- **XSS** - Unsanitized user input in output58- **Insecure Deserialization** - Unsafe object serialization59- **Vulnerable Dependencies** - Known CVEs in dependencies60- **Insufficient Logging** - Missing audit trails6162#### Code-Level Security63- **Secret Management** - Hardcoded API keys, passwords64- **Input Validation** - Missing or weak validation65- **Output Encoding** - Proper escaping for context66- **Error Handling** - Information leakage in errors67- **Cryptography** - Weak algorithms, improper usage6869### 3. Performance Analysis7071Identify performance concerns:7273#### Code Efficiency74- **Algorithm Complexity** - O(n²) or worse patterns75- **Memory Leaks** - Unclosed resources, unbounded caches76- **N+1 Queries** - Database query patterns77- **Unnecessary Operations** - Redundant computations7879#### Resource Management80- **Connection Pooling** - Database, HTTP connections81- **Caching Strategy** - Missing or ineffective caching82- **Async Operations** - Blocking calls in async contexts83- **Bundle Size** - Large dependencies, unused imports (frontend)8485#### Scalability Concerns86- **State Management** - Stateful components that prevent scaling87- **Race Conditions** - Concurrent access patterns88- **Resource Limits** - Hardcoded limits, unbounded growth8990### 4. Code Stability9192Assess reliability and maintainability:9394#### Test Coverage95- **Unit Tests** - Coverage percentage, critical path coverage96- **Integration Tests** - API and service integration testing97- **E2E Tests** - User journey coverage98- **Test Quality** - Assertions, edge cases, mocking patterns99100#### Error Handling101- **Exception Coverage** - Unhandled exceptions102- **Graceful Degradation** - Fallback mechanisms103- **Recovery Patterns** - Retry logic, circuit breakers104- **Error Reporting** - Proper error classification and logging105106#### Code Quality107- **Type Safety** - TypeScript strict mode, type coverage108- **Null Safety** - Null/undefined handling109- **Documentation** - Critical function documentation110- **TODO/FIXME** - Outstanding technical debt markers111112## Health Score Calculation113114Generate a health score (0-100) based on weighted categories:115116| Category | Weight | Metrics |117|----------|--------|---------|118| Structure | 25% | Architecture consistency, code organization, complexity |119| Security | 30% | Vulnerability count, secret exposure, dependency health |120| Performance | 20% | Efficiency patterns, resource management |121| Stability | 25% | Test coverage, error handling, type safety |122123### Scoring Rubric124125**Structure (25 points)**126- 25: Clean architecture, consistent patterns, low complexity127- 20: Minor inconsistencies, acceptable complexity128- 15: Some architectural issues, moderate complexity129- 10: Significant structural problems130- 5: Major architectural issues, high complexity131132**Security (30 points)**133- 30: No vulnerabilities, proper secret management, secure patterns134- 24: Minor security concerns, no critical issues135- 18: Some vulnerabilities, needs attention136- 12: Multiple security issues137- 6: Critical security vulnerabilities138139**Performance (20 points)**140- 20: Efficient code, proper resource management141- 16: Minor inefficiencies142- 12: Some performance concerns143- 8: Significant performance issues144- 4: Major performance problems145146**Stability (25 points)**147- 25: High test coverage (>80%), comprehensive error handling148- 20: Good coverage (60-80%), adequate error handling149- 15: Moderate coverage (40-60%), basic error handling150- 10: Low coverage (20-40%), minimal error handling151- 5: Very low coverage (<20%), poor error handling152153## Output Format154155Generate a comprehensive health report:156157```markdown158# Project Health Report159160## Summary161- **Overall Health Score**: XX/100162- **Risk Level**: Low/Medium/High/Critical163- **Assessment Date**: YYYY-MM-DD164165## Category Scores166| Category | Score | Status |167|----------|-------|--------|168| Structure | XX/25 | 🟢/🟡/🔴 |169| Security | XX/30 | 🟢/🟡/🔴 |170| Performance | XX/20 | 🟢/🟡/🔴 |171| Stability | XX/25 | 🟢/🟡/🔴 |172173## Critical Issues (Immediate Action Required)1741. [Issue description with file:line reference]1752. ...176177## High Priority Issues1781. [Issue description]1792. ...180181## Medium Priority Issues1821. [Issue description]1832. ...184185## Recommendations1861. [Actionable recommendation]1872. ...188189## Detailed Findings190191### Structure Analysis192[Detailed findings]193194### Security Analysis195[Detailed findings]196197### Performance Analysis198[Detailed findings]199200### Stability Analysis201[Detailed findings]202```203204## Integration with CI/CD205206This skill can be used to:207- Generate reports for code review208- Block PRs with critical issues209- Track health metrics over time210- Set quality gates for releases211212## Related Skills213214- `analyze-codebase` - Deep architectural analysis215- `security-audit` - Detailed security review216- `performance-review` - Performance profiling217- `test-coverage` - Test coverage analysis218219---220> Converted and distributed by [TomeVault](https://tomevault.io/claim/runxgalee) — claim your Tome and manage your conversions.221<!-- tomevault:4.0:skill_md:2026-04-15 -->