Agent skill · writing content · aiskillstore
code-reviewer
Provides thorough code review guidance when users ask for code reviews, PR reviews, or feedback on their code. Activates when users mention reviewing code, checking for issues, or want feedback on implementations.
Why this skill is useful
Codifies a structured approach to code reviews that the AI could infer but now doesn't have to guess.
What it needs
About 2k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Code Reviewer Purpose Provides comprehensive code review following industry best practices, focusing on code quality, security, performance, and maintainability. When It Activates User asks to review code or a pull request User wants feedback on their implementation User mentions code quality checks User asks "can you review this code?" Instructions When reviewing code, systematically analyze: 1. Code Quality Readability: Is the code clear and self-documenting? Naming: Are variables, functions, and classes well-named? Complexity: Are there overly complex sections that need refactoring? DRY Principle: Is there unnecessary code duplication? 2. Best Practices Language idioms: Does it follow language-specific conventions? Design patterns: Are appropriate patterns used correctly? Error handling: Are errors properly caught and handled? Logging: Is there adequate logging for debugging? 3. Security Input validation: Are all inputs properly validated? SQL injection: Are database queries parameterized? XSS vulnerabilities: Is output properly escaped? Authentication/Authorization: Are permissions checked? Sensitive data: Are secrets properly protected? 4. Performance Algorithmic complexity: Can performance be improved? Database queries: Are they efficient (N+1 queries)? Memory usage: Are there potential memory leaks? Caching: Could caching improve performance? 5. Testing Test coverage: Are there tests for new functionality? Edge cases: Are edge cases covered? Test quality: Are tests meaningful and maintainable? 6. Documentation Comments: Are complex sections explained? API docs: Are public interfaces documented? README updates: Does documentation need updating? Review Format Present findings as: 1. Summary: Quick overview of the review 2. Strengths: What's done well 3. Issues Found: Organized by severity (Critical, Major, Minor) 4. Recommendations: Specific, actionable improvements 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/code-reviewer--977313