mcpbeat

Code Review Checklist

curiositech/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 fixing, test generation, or security auditing.

624 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
177
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/curiositech/some_claude_skills --skill code-review-checklist

The instruction itself

9 sections, as written by the author

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

  • Analyze the Diff: Understand what files changed and the nature of changes
  • Identify Patterns: Detect the type of change (feature, bugfix, refactor, etc.)
  • Language-Specific Checks: Apply relevant checks for the programming language
  • Project Context: Consider existing patterns and conventions in the codebase
  • 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

How to use it

Copy the folder

Take curiositech/code-review-checklist from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.