code-review

fwdslsh's avatarfrom fwdslsh

Provides thorough code review with actionable feedback

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 15, 2025

When & Why to Use This Skill

This Claude skill automates the code review process by providing comprehensive, actionable feedback on source code. It systematically evaluates code quality, security vulnerabilities, performance bottlenecks, and maintainability, ensuring that every pull request meets high engineering standards while significantly reducing the manual workload for senior developers.

Use Cases

  • Pre-merge Code Audits: Automatically analyze pull requests to identify bugs, style violations, and architectural flaws before they reach production.
  • Security Compliance Checks: Scan code for common vulnerabilities such as SQL injection, XSS, and insecure data handling to ensure robust application security.
  • Performance Tuning: Detect inefficient algorithms, unnecessary iterations, and database query issues to optimize system responsiveness and resource usage.
  • Technical Debt Management: Enforce coding best practices like DRY and SOLID principles to maintain a clean, readable, and scalable codebase.
namecode-review
descriptionProvides thorough code review with actionable feedback
allowed-toolsRead, Grep, Glob

Code Review Skill

Purpose

Perform thorough code reviews that identify issues and suggest improvements.

Review Checklist

When reviewing code, check for:

Code Quality

  • Clear variable and function names
  • DRY (Don't Repeat Yourself) principles
  • Single responsibility principle
  • Appropriate error handling

Security

  • Input validation
  • SQL injection prevention
  • XSS prevention
  • Sensitive data handling

Performance

  • Unnecessary loops or iterations
  • Database query optimization
  • Memory leaks
  • Caching opportunities

Maintainability

  • Code documentation
  • Test coverage
  • Consistent coding style
  • Clear module boundaries

Feedback Format

Provide feedback in this format:

  1. Issue: Description of the problem
  2. Location: File and line number
  3. Severity: Critical/Major/Minor/Suggestion
  4. Fix: Recommended solution