code-review

Provides expert code review guidelines and best practices

⭐5stars🔀0forks📁View on GitHub🕐Updated Jan 3, 2026

When & Why to Use This Skill

This Claude skill provides a comprehensive framework for expert code reviews, focusing on correctness, readability, performance, and security. It empowers developers and teams to maintain high-quality codebases by providing structured checklists and actionable guidelines to identify common anti-patterns such as duplicated code, poor naming conventions, and missing error handling.

Use Cases

  • Automated Pull Request Audits: Systematically evaluate code changes for security vulnerabilities, performance bottlenecks, and logic correctness using a standardized checklist.
  • Technical Mentorship: Apply constructive review guidelines to provide high-quality, empathetic feedback to team members, fostering a culture of continuous learning and improvement.
  • Refactoring Legacy Code: Identify 'code smells' like magic numbers, deep nesting, and hardcoded values to guide the modernization and cleanup of existing software.
  • Standardizing Engineering Practices: Implement the provided best practices as a team-wide standard to ensure consistency in documentation and code structure across different projects.
namecode-review
descriptionProvides expert code review guidelines and best practices

Code Review Skill

When reviewing code, follow these best practices:

Review Checklist

  1. Correctness: Does the code work as intended?
  2. Readability: Is the code easy to understand?
  3. Performance: Are there any obvious performance issues?
  4. Security: Are there any security vulnerabilities?
  5. Testing: Is the code adequately tested?
  6. Documentation: Is the code well-documented?

Review Guidelines

  • Be constructive and kind
  • Focus on the code, not the coder
  • Suggest improvements, don't just criticize
  • Explain the "why" behind your suggestions
  • Prioritize issues by severity

Common Issues to Look For

  • Magic numbers and strings
  • Duplicated code
  • Long functions or methods
  • Deep nesting
  • Missing error handling
  • Hardcoded values
  • Poor naming conventions