Skill

code-review-checklist

Systematic code review process, feedback templates, approval criteria, and review best practices.

Install

Run in your terminal

npx claudepluginhub sethdford/claude-skills --plugin engineer-toolkit

Tool Access

This skill uses the workspace's default tool permissions.

Skill Content

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

157.6k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

157.6k

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

138.7k

Stats

Parent Repo Stars3

Parent Repo Forks0

Last CommitMar 11, 2026

Actions

View Source View Plugin View on GitHub View README

Instructions

Correctness: Does this solve the problem? Are edge cases handled?

Tests: Are tests comprehensive? Do they test behavior, not implementation?

Code Quality: Naming clear? Functions small? DRY?

Performance: Any N+1 queries? Unnecessary copying?

Security: No secrets? No SQL injection? Safe input handling?

Comments: Only if explaining why, not what

Approval: Is this good enough to merge?

Code Review Checklist

Conducting effective code reviews that improve quality and share knowledge.

Context

You are reviewing code. Be thorough but kind; goal is learning and quality.

Domain Context

Correctness: Does code do what it claims?
Testing: Are there tests? Do they cover important cases?
Readability: Can a new person understand it?
Performance: Is it efficient? Any obvious issues?
Security: Are there security risks?
Style: Does it follow team conventions?

Instructions

Correctness: Does this solve the problem? Are edge cases handled?
Tests: Are tests comprehensive? Do they test behavior, not implementation?
Code Quality: Naming clear? Functions small? DRY?
Performance: Any N+1 queries? Unnecessary copying?
Security: No secrets? No SQL injection? Safe input handling?
Comments: Only if explaining why, not what
Approval: Is this good enough to merge?

Anti-Patterns

Blocking on style; use linters instead
Nitpicking without understanding context
Vague feedback ("improve this"); be specific
Ignoring tests; they're critical
Approving without reading code
Personal criticism ("you always do this"); focus on code

code-review-checklist

code-review-checklist

Code Review Checklist

Context

Domain Context

Instructions

Anti-Patterns

Further Reading

Code Review Checklist

Context

Domain Context

Instructions

Anti-Patterns

Further Reading