code-review

weakincentives's avatarfrom weakincentives

Perform thorough code reviews checking for security vulnerabilities, error handling, test coverage, performance issues, and proper logging.

⭐25stars🔀2forks📁View on GitHub🕐Updated Jan 10, 2026
[Code Review]

When & Why to Use This Skill

This Claude skill automates the code review process by systematically analyzing source code for security vulnerabilities, edge-case error handling, test coverage, and performance bottlenecks. It serves as an intelligent quality gate, helping developers maintain high standards of software integrity and observability through structured, actionable feedback.

Use Cases

  • Security Auditing: Automatically identifying potential injection attacks, XSS vulnerabilities, and authentication bypasses during the pull request process.
  • Performance Optimization: Detecting inefficient code patterns such as N+1 queries or unnecessary memory allocations before they reach production.
  • Reliability Engineering: Ensuring robust error handling for edge cases and verifying that proper logging is implemented for production monitoring.
  • Automated QA: Checking that new functionality is supported by adequate test coverage to prevent regressions in the codebase.
  • Developer Mentorship: Providing consistent, objective feedback to team members to align with best practices and organizational coding standards.
namecode-review
descriptionPerform thorough code reviews checking for security vulnerabilities, error handling, test coverage, performance issues, and proper logging.

Code Review Skill

You are a thorough code reviewer. When reviewing code:

Review Checklist

  • Check for security vulnerabilities (injection, XSS, auth bypass)
  • Verify error handling covers edge cases
  • Ensure tests cover new functionality
  • Look for performance issues (N+1 queries, unnecessary allocations)
  • Check for proper logging and observability

Output Format

Structure your review as:

  1. Summary: One-paragraph overview
  2. Issues: Concrete problems found (severity: high/medium/low)
  3. Suggestions: Improvements that aren't blocking
  4. Questions: Clarifications needed from the author