Agent skill · software engineering · aiskillstore
code-review
Conduct thorough, constructive code reviews for quality and security. Use when reviewing pull requests, checking code quality, identifying bugs, or auditing security. Handles best practices, SOLID principles, security vulnerabilities, performance analysis, and testing coverage.
Why this skill is useful
Provides a structured approach to code reviews that includes security, performance, and testing considerations, which the AI may not generate independently.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Code Review When to use this skill Reviewing pull requests Checking code quality Providing feedback on implementations Identifying potential bugs Suggesting improvements Security audits Performance analysis Instructions Step 1: Understand the context Read the PR description: What is the goal of this change? Which issues does it address? Are there any special considerations? Check the scope: How many files changed? What type of changes? (feature, bugfix, refactor) Are tests included? Step 2: High-level review Architecture and design: Does the approach make sense? Is it consistent with existing patterns? Are there simpler alternatives? Is the code in the right place? Code organization: Clear separation of concerns? Appropriate abstraction levels? Logical file/folder structure? Step 3: Detailed code review Naming: [ ] Variables: descriptive, meaningful names [ ] Functions: verb-based, clear purpose [ ] Classes: noun-based, single responsibility [ ] Constants: UPPERCASE for true constants [ ] Avoid abbreviations unless widely known Functions: [ ] Single responsibility [ ] Reasonable length (< 50 lines ideally) [ ] Clear inputs and outputs [ ] Minimal side effects [ ] Proper error handling Classes and objects: [ ] Single responsibility principle [ ] Open/closed principle [ ] Liskov substitution principle [ ] Interface segregation [ ] Dependency inversion Error handling: [ ] All errors caught and handled [ ] Meaningful error messages [ ] Proper logging [ ] No silent failures [ ] User-friendly errors for UI Code quality: [ ] No code duplication (DRY) [ ] No dead code [ ] No commented-out code [ ] No magic numbers [ ] Consistent formatting Step 4: Security review Input validation: [ ] All user inputs validated [ ] Type checking [ ] Range checking [ ] Format validation Authentication & Authorization: [ ] Proper authentication checks [ ] Authorization for sensitive operations [ ] Session management [ ] Password handling (hashing, salting) Data protection: [ ] No hardcoded sec …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/code-review--d59920