๐Code Review Skills
Browse the best Code Review skills for Claude Code, Codex, Cursor and other AI agents.
2,558 skills ยท Page 4 of 107
python-typing-patterns
Python type hints and type safety patterns. Triggers on: type hints, typing, TypeVar, Generic, Protocol, mypy, pyright, type annotation, overload, TypedDict.
ruff
This skill should be used when users need to lint, format, or validate Python code using the Ruff command-line tool. Use this skill for tasks involving Python code quality checks, automatic code formatting, enforcing style rules (PEP 8), identifying bugs and security issues, or modernizing Python code. This skill should be invoked PROACTIVELY whenever Python code is written or modified to ensure code quality.
clean-code
Clean code principles including descriptive variable naming and YAGNI (You Aren't Gonna Need It). Use this when writing or refactoring code.
golangci-lint
Configure and run golangci-lint
code-review-checklist
Apply comprehensive code review checklist covering purpose, design, quality, correctness, security, performance, testing, and documentation. Use when reviewing pull requests, conducting code reviews, or self-reviewing changes before committing.
django-conventions
Comprehensive Django best practices covering project structure, models (field choices, Meta options, managers, QuerySets, migrations), views (CBVs vs FBVs, generic views), Django REST Framework (serializers, ViewSets, permissions), forms, templates, security (CSRF, XSS, SQL injection), performance (N+1 queries, select_related, prefetch_related, caching), testing, and common anti-patterns. Essential reference for Django code reviews and development.
performance-optimizer
Expert performance analysis and optimization. Use when analyzing performance issues, optimizing slow code, reducing bundle size, or improving application speed.
global-coding-style
Write clean, consistent code following established naming conventions, formatting rules, and the DRY principle across all files. Use this skill when writing any code in any file, naming variables and functions, structuring code logic, formatting code with consistent indentation, choosing descriptive names that reveal intent, keeping functions small and focused, removing dead code and unused imports, extracting common logic into reusable functions, maintaining consistent code style across the codebase, configuring linters and formatters, or refactoring code for better readability. Apply this skill universally across all coding tasks to ensure code quality, maintainability, and consistency with project standards. This skill should be active for all file types including TypeScript, JavaScript, Python, Ruby, Java, Go, and other programming languages.
vue
Vue.js development best practices including Composition API, state management, and performance.
programming-common
General programming best practices applicable to all languages. Covers clean code, testing, refactoring, version control, and development workflows. Use when writing or reviewing code in any language.
react-native-performance
React Native performance optimization techniques. Use when optimizing app performance.
refactoring
Identifies code smells, applies design patterns, guides migrations, and performs security/performance/accessibility refactoring. Use when improving code quality, modernizing codebases, applying design patterns, migrating to TypeScript, or extracting microservices.
Vercel React Best Practices
A powerful skill for Claude agents.
move-code-quality
Analyzes Move language packages against the official Move Book Code Quality Checklist. Use this skill when reviewing Move code, checking Move 2024 Edition compliance, or analyzing Move packages for best practices. Activates automatically when working with .move files or Move.toml manifests.
typescript
TypeScript code style, type co-location, constant naming conventions, and arktype patterns. Use when writing TypeScript code, defining types, creating constants, or working with arktype schemas.
review
Comprehensive code review workflow - parallel specialized reviews โ synthesis
code-review
Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers three practices - receiving feedback with technical rigor over performative agreement, requesting reviews via code-reviewer subagent, and verification gates requiring evidence before any status claims. Essential for subagent-driven development, pull requests, and preventing false completion claims.
codex-claude-loop
Orchestrates a dual-AI engineering loop where Claude Code plans and implements, while Codex validates and reviews, with continuous feedback for optimal code quality
reviewing-code
Systematically evaluate code changes for security, correctness, performance, and spec alignment. Use when reviewing PRs, assessing code quality, or verifying implementation against requirements.
coding-standards
ใณใผใใฎๅ่ณชๅ้กใใขใณใใใฟใผใณใๅฏ่ชญๆงใๆคๆปใๆฉ่ฝๅฎ่ฃ ใใณใผใใฌใใฅใผใใชใใกใฏใฟใชใณใฐๆใซไฝฟ็จใ
safe-refactoring
Systematic code refactoring while preserving all external behavior.Use when identifying code smells, planning refactoring sequences,executing safe structural improvements, or validating behavior preservation.Includes code smell catalog (reference.md) and refactoring execution protocol.
review-implementing
Process and implement code review feedback systematically. Use when user provides reviewer comments, PR feedback, code review notes, or asks to implement suggestions from reviews.
software-design-principles
Object-oriented design principles including object calisthenics, dependency inversion, fail-fast error handling, feature envy detection, and intention-revealing naming. Activates during code refactoring, design reviews, or when user requests design improvements.
swift-concurrency
Expert guidance on Swift Concurrency best practices, patterns, and implementation. Use when developers mention: (1) Swift Concurrency, async/await, actors, or tasks, (2) "use Swift Concurrency" or "modern concurrency patterns", (3) migrating to Swift 6, (4) data races or thread safety issues, (5) refactoring closures to async/await, (6) @MainActor, Sendable, or actor isolation, (7) concurrent code architecture or performance optimization.