code-reviewer

Review code diffs and pull requests for bugs, security issues, and best practice violations.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/AdeptMind/pr-emojis-in-slack --skill code-reviewer-adeptmind
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/AdeptMind/pr-emojis-in-slack/tree/main/.claude/skills/code-reviewer
Command: npx skills add https://github.com/AdeptMind/pr-emojis-in-slack --skill code-reviewer-adeptmind

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of reviewing code changes, identifying potential bugs, security vulnerabilities, and deviations from best practices, thereby improving overall code quality and maintainability.

Core Features & Use Cases

  • Comprehensive Code Analysis: Analyzes code for adherence to principles like DRY, KISS, and SOLID.
  • Issue Identification: Detects bugs, security flaws, readability issues, and dead code.
  • Use Case: Before merging a pull request, use this Skill to perform a thorough review, ensuring that the new code is robust, secure, and follows established coding standards.

Quick Start

Review the code changes in the provided pull request URL.

Frequently Asked Questions about code-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a pull request for bugs and security vulnerabilities before merging?

Reviewing code changes for best practice violations involves checking diffs against DRY, KISS, and SOLID principles to detect logic errors, security vulnerabilities, and maintainability concerns. This analysis identifies dead code and readability issues while providing structured severity levels and auto-fix suggestions.

What is the best way to automate code analysis for DRY, KISS, and SOLID principles?

Automating code analysis for DRY, KISS, and SOLID principles involves processing code diffs to identify deviations from established coding standards. The analysis detects bugs, security flaws, and readability issues, returning structured output with severity levels and actionable auto-fix suggestions.

Can I use automated code review to detect dead code and readability issues in my diffs?

Yes, automated code review can detect dead code and readability issues in your diffs. By analyzing code changes for adherence to established coding standards, it identifies potential bugs, security vulnerabilities, and maintainability concerns while providing structured severity levels and auto-fix suggestions.

Does code review support structured output with severity levels and auto-fix suggestions?

Code review supports structured output with severity levels and auto-fix suggestions. It analyzes code changes, diffs, or pull requests for bugs, security issues, and best practice violations, identifying logic errors and maintainability concerns while returning actionable remediation steps.

When do I need to perform a comprehensive code review on my code changes?

You need to perform a comprehensive code review on your code changes before merging a pull request to ensure new code is robust, secure, and follows established coding standards. This identifies potential bugs, security vulnerabilities, and deviations from DRY, KISS, and SOLID principles.