Code Review Checklist Generator

## ROLE
You are a senior developer who ensures high code quality through thorough reviews.

## CONTEXT
I need a code review checklist for:

**Review Context:**
- Project Type: [PROJECT_TYPE]
- Language/Framework: [LANGUAGE_FRAMEWORK]
- Team Experience: [TEAM_LEVEL]
- Focus Areas: [FOCUS_AREAS]
- Compliance Needs: [COMPLIANCE]

## TASK
Generate comprehensive code review checklist:

### 1. GENERAL CODE QUALITY
- [ ] Code follows project style guide
- [ ] No unnecessary code duplication (DRY)
- [ ] Functions/methods are focused and small
- [ ] Variable/function names are descriptive
- [ ] Complex logic has explanatory comments
- [ ] No dead code or commented-out code
- [ ] No TODO comments without tickets

### 2. FUNCTIONALITY
- [ ] Code does what the ticket/PR describes
- [ ] Edge cases are handled
- [ ] Error scenarios are covered
- [ ] No breaking changes (or documented)
- [ ] Backwards compatibility maintained

### 3. TESTING
- [ ] Unit tests added/updated
- [ ] Integration tests if needed
- [ ] Test coverage meets threshold ([X]%)
- [ ] Tests are readable and maintainable
- [ ] Edge cases have test coverage
- [ ] Tests don't have false positives

### 4. SECURITY
- [ ] No secrets in code
- [ ] Input validation present
- [ ] Output encoding for XSS prevention
- [ ] SQL injection prevention
- [ ] Authentication/authorization checked
- [ ] Sensitive data handled properly
- [ ] Dependencies are secure (no vulns)

### 5. PERFORMANCE
- [ ] No N+1 queries
- [ ] Appropriate indexes used
- [ ] No unnecessary database calls
- [ ] Caching considered
- [ ] Large data sets paginated
- [ ] Async operations where beneficial

### 6. [LANGUAGE_FRAMEWORK] SPECIFIC
[FRAMEWORK_SPECIFIC_CHECKLIST]

### 7. DOCUMENTATION
- [ ] README updated if needed
- [ ] API documentation updated
- [ ] Inline documentation for complex code
- [ ] CHANGELOG updated

### 8. DEPLOYMENT
- [ ] Migrations are reversible
- [ ] Feature flags if needed
- [ ] Environment variables documented
- [ ] No hardcoded values

### 9. FINAL CHECKS
- [ ] PR description is clear
- [ ] Commits are atomic and well-messaged
- [ ] No merge conflicts
- [ ] CI/CD pipeline passes

## RULES
- Review for correctness first
- Then maintainability
- Then performance
- Be constructive, not critical
- Suggest, don't demand