code-reviewer

Analyze code diffs to identify bugs, security risks, and maintainability issues.

8|4|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/adrien-barret/claude-kit --skill code-reviewer-adrien-barret
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/adrien-barret/claude-kit/tree/main/project-template/.claude/skills/code-reviewer
Command: npx skills add https://github.com/adrien-barret/claude-kit --skill code-reviewer-adrien-barret

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams identify bugs, security issues, and maintainability concerns in code changes before merging.

Core Features & Use Cases

  • Automated review prompts: highlights DRY, KISS, SOLID violations, and readability issues.
  • Security & quality checks: flags potential vulnerabilities and architectural concerns in diffs.
  • Use Case: When you open a PR, run this Skill to obtain a concise set of findings with actionable fixes.

Quick Start

Provide the PR URL or diff to initiate an automated review and receive a structured findings report.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I automate code review for pull requests?

Automated code review for pull requests is performed by analyzing diffs to identify bugs, security risks, and maintainability issues before merge. You provide a PR URL or diff to receive a structured findings report with severity levels and actionable fixes.

What is static analysis for code maintainability?

Static analysis for code maintainability involves examining code changes to flag DRY, KISS, and SOLID violations alongside readability issues. It highlights architectural concerns in diffs to help reviewers catch structural problems early.

Can I run security checks on code diffs across different programming languages?

Security checks on code diffs can be applied across languages to flag potential vulnerabilities. The analysis examines patches and commits to identify security risks, providing actionable recommendations before merging.

What's the best way to catch bugs in commits before merging?

The best way to catch bugs in commits before merging is to run automated analysis on the code changes. This process identifies bugs and security issues, enforcing structured findings with severity levels to guide fixes.

Does automated code review work with just a diff or patch?

Automated code review works with just a diff or patch by analyzing the provided changes to highlight maintainability concerns and potential vulnerabilities. Submitting the diff initiates the review to generate a concise findings report.