Code Review Checklist Agent Skill

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

files

instructions only

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

Other skills for the same job

different authors, same section of the catalogue

Receiving Code Review

by ZhanlinCui

×7

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

2k tokens

Requesting Code Review

by ZhanlinCui

×6

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

Comprehensive GitHub code review with AI-powered swarm coordination

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens

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.