OpenSkillIndex← back to search
claude-code

Some_claude_skills code-review-checklist

Generate context-aware code review checklists from PR diffs — tailored to language, codebase patterns, and team standards. Identifies what reviewers should focus on. NOT for automated code

install
source · Clone the upstream repo
git clone https://github.com/curiositech/some_claude_skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/curiositech/some_claude_skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.claude/skills/code-review-checklist" ~/.claude/skills/erichowens-some-claude-skills-code-review-checklist && rm -rf "$T"
manifest: .claude/skills/code-review-checklist/SKILL.md
source content

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 level