Generates comprehensive, context-aware code review checklists tailored to the specific codebase, programming language, and team standards. Analyzes PR diffs and suggests what reviewers should focus on.
Scanned 2/12/2026
Install via CLI
openskills install erichowens/some_claude_skills---
name: code-review-checklist
description: Generates comprehensive, context-aware code review checklists tailored to the specific codebase, programming language, and team standards. Analyzes PR diffs and suggests what reviewers should focus on.
category: Code Quality & Testing
tags:
- code-review
- quality
- checklist
- pr-review
- best-practices
allowed-tools: Read, Grep, Glob
---
# Code Review Checklist Generator
Generate thorough, contextual code review checklists that help reviewers focus on what matters most for each specific PR.
## When to Use
- Before starting a code review to know what to look for
- When onboarding new team members to review standards
- To ensure consistent review quality across the team
- When reviewing unfamiliar parts of the codebase
## Approach
1. **Analyze the Diff**: Understand what files changed and the nature of changes
2. **Identify Patterns**: Detect the type of change (feature, bugfix, refactor, etc.)
3. **Language-Specific Checks**: Apply relevant checks for the programming language
4. **Project Context**: Consider existing patterns and conventions in the codebase
5. **Generate Checklist**: Produce prioritized, actionable review items
## Checklist Categories
### Security
- [ ] Input validation present
- [ ] No hardcoded secrets or credentials
- [ ] Proper authentication/authorization checks
- [ ] SQL injection prevention
- [ ] XSS prevention for web code
### Performance
- [ ] No N+1 query patterns
- [ ] Appropriate caching considered
- [ ] No unnecessary loops or iterations
- [ ] Efficient data structures used
### Maintainability
- [ ] Code is readable and self-documenting
- [ ] Functions are appropriately sized
- [ ] No code duplication
- [ ] Consistent naming conventions
### Testing
- [ ] Unit tests cover new functionality
- [ ] Edge cases are tested
- [ ] Tests are meaningful, not just for coverage
## Best Practices
- Prioritize security issues first
- Focus on logic errors over style nitpicks
- Consider the reviewer's time - highlight critical items
- Adapt checklist to project maturity levelNo comments yet. Be the first to comment!
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.
Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits. Triggers: remove dead code, dead code, cleanup, remove unused.
Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.
一个全面的 Claude Code 会话验证系统。