code-review

DCRepairCenter's avatarfrom DCRepairCenter

Code review assistant. Use to review code changes, identify issues, and provide improvement suggestions with priority levels.

⭐0stars🔀1forks📁View on GitHub🕐Updated Jan 1, 2026
[Code Review]

When & Why to Use This Skill

This Claude skill serves as a comprehensive automated code review assistant, designed to enhance software quality by analyzing code changes for architectural integrity, security vulnerabilities, and performance efficiency. It provides structured, prioritized feedback ranging from critical fixes to optimization suggestions, ensuring adherence to industry best practices like SOLID, DRY, and KISS principles.

Use Cases

  • Automated Pull Request Auditing: Streamline the peer review process by automatically identifying code smells, naming inconsistencies, and logic errors in git diffs.
  • Security and Safety Compliance: Proactively detect exposed secrets, missing input validations, and improper error handling before code reaches production.
  • Architectural Governance: Ensure new code contributions adhere to specific project structures, such as proper layer separation and contract compliance.
  • Performance and Efficiency Checks: Identify potential memory leaks, inefficient async operations, and tier-inappropriate response times in new feature implementations.
namecode-review
descriptionCode review assistant. Use to review code changes, identify issues, and provide improvement suggestions with priority levels.

Code Review Skill

Review code changes and provide structured feedback.

Analysis Areas

  1. Code Quality

    • KISS, YAGNI, DRY principles
    • SOLID compliance
    • Clear naming and documentation

  2. Architecture

    • Layer separation (core/agent/ai/gui)
    • Proper use of contracts from rainze.core.contracts
    • UCM entry rule compliance

  3. Safety & Security

    • Input validation
    • Error handling
    • No exposed secrets

  4. Performance

    • Appropriate tier for response time
    • Memory efficiency
    • Async usage where appropriate

  5. Tests

    • Coverage of new functionality
    • Edge cases handled

Output Format

Organize feedback by priority:

  • 🔴 Critical (must fix)
  • 🟡 Warning (should fix)
  • 🟢 Suggestion (consider)

Include specific file:line references and code examples for fixes.

Review Workflow

  1. Run git diff or git diff --cached to see changes
  2. Analyze each changed file
  3. Check for violations of coding standards
  4. Verify test coverage
  5. Summarize findings with priorities