Reorder folders based on learning dependencies, complexity, and frequency of use: - 01-slash-commands (unchanged) - Quick wins for beginners - 02-memory (was 03) - Essential foundation - 03-skills (was 05) - Auto-invoked capabilities - 04-subagents (was 02) - Task delegation - 05-mcp (was 04) - External integration - 06-hooks (was 07) - Event automation - 07-plugins (was 06) - Bundled solutions - 08-checkpoints (unchanged) - Safe experimentation - 09-advanced-features (unchanged) - Power user tools Documentation improvements: - Add LEARNING-ROADMAP.md with detailed milestones and exercises - Simplify README.md for better scannability - Consolidate Quick Start and Getting Started sections - Combine Feature Comparison and Use Case Matrix tables - Reorder README sections: Learning Path → Quick Reference → Getting Started - Update all cross-references across module READMEs 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
1.4 KiB
1.4 KiB
Code Review Checklist
Security Checklist
- No hardcoded credentials or secrets
- Input validation on all user inputs
- SQL injection prevention (parameterized queries)
- CSRF protection on state-changing operations
- XSS prevention with proper escaping
- Authentication checks on protected endpoints
- Authorization checks on resources
- Secure password hashing (bcrypt, argon2)
- No sensitive data in logs
- HTTPS enforced
Performance Checklist
- No N+1 queries
- Appropriate use of indexes
- Caching implemented where beneficial
- No blocking operations on main thread
- Async/await used correctly
- Large datasets paginated
- Database connections pooled
- Regular expressions optimized
- No unnecessary object creation
- Memory leaks prevented
Quality Checklist
- Functions < 50 lines
- Clear variable naming
- No duplicate code
- Proper error handling
- Comments explain WHY, not WHAT
- No console.logs in production
- Type checking (TypeScript/JSDoc)
- SOLID principles followed
- Design patterns applied correctly
- Self-documenting code
Testing Checklist
- Unit tests written
- Edge cases covered
- Error scenarios tested
- Integration tests present
- Coverage > 80%
- No flaky tests
- Mock external dependencies
- Clear test names