Agent skill · software engineering · aiskillstore
code-review
Perform comprehensive code reviews covering security, style, performance, and best practices. Use when reviewing code changes before commit or merge, auditing existing code, or checking for vulnerabilities.
Why this skill is useful
Provides a structured approach to code reviews, including security checks and performance optimizations that the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Skill: code-review Purpose: Perform comprehensive code reviews covering security, style, performance, and best practices. When to use this Skill Use this Skill when: Reviewing code changes before commit or merge. Auditing existing code for issues. Checking for security vulnerabilities. Ensuring code follows project conventions. Review workflow 1. Gather context Before reviewing: Understand: What is the purpose of these changes? Which files are affected? What is the expected behavior? 2. Security audit Check for: [ ] Injection vulnerabilities: SQL, command, XSS. [ ] Authentication issues: Weak auth, missing checks. [ ] Authorization flaws: Missing permission checks. [ ] Sensitive data exposure: Hardcoded secrets, logs. [ ] Insecure dependencies: Known vulnerabilities. Red flags: String concatenation in queries. eval(), exec(), or similar. Hardcoded credentials or API keys. Missing input validation. Overly permissive CORS. 3. Style check Verify: [ ] Naming conventions: Clear, consistent names. [ ] Code formatting: Consistent indentation, spacing. [ ] Documentation: Comments where needed. [ ] File organization: Logical structure. [ ] Import ordering: Consistent imports. 4. Performance review Look for: [ ] N+1 queries: Database access in loops. [ ] Unnecessary computation: Repeated calculations. [ ] Memory issues: Large allocations, leaks. [ ] Blocking operations: Sync in async contexts. [ ] Inefficient algorithms: O(n²) where O(n) possible. 5. Best practices Check: [ ] Error handling: Proper try/catch, error types. [ ] Logging: Appropriate log levels. [ ] Testing: Test coverage for changes. [ ] DRY principle: No unnecessary duplication. [ ] Single responsibility: Functions do one thing. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/code-review--8ca30f