mcpField
C
code-review-checklist

code-review-checklist

github.com/curiositechTesting & quality257175 installsUpdated 1d ago
Repository

About code-review-checklist

A skill for generating prioritized, actionable code review checklists tailored to a pull request’s changes, language, and project conventions. It helps reviewers focus on security, correctness, and maintainability.

Key features

  1. 01Analyzes changed files and change type
  2. 02Applies language-specific checks
  3. 03Accounts for project conventions
  4. 04Prioritizes actionable review items
  5. 05Covers security, performance, testing, and maintainability

Use cases

  1. 01Preparing a focused checklist before reviewing a pull request
  2. 02Aligning review standards when onboarding teammates
  3. 03Reviewing unfamiliar areas of a codebase

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/curiositech/some_claude_skills --skill code-review-checklist

After installing, type/code-review-checklistin Claude Code to confirm it loaded.

Bundled files.claude-plugin/plugin.json

Details

From the project README

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

Comments

Markdown supported