code-reviewer

Identify code quality issues and security risks in diffs.

45|3|Updated Jul 10, 2023
One-click install
npx skills add https://github.com/incubateur-ademe/benefriches --skill code-reviewer-incubateur-ademe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/incubateur-ademe/benefriches/tree/main/.claude/skills/code-reviewer
Command: npx skills add https://github.com/incubateur-ademe/benefriches --skill code-reviewer-incubateur-ademe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the detection of code quality issues, security vulnerabilities, and maintainability problems in recent changes, reducing manual review time and human error.

Core Features & Use Cases

  • Security & Vulnerability Checks: surface potential risks in diffs and advise mitigations.
  • Maintainability & Consistency: enforce project patterns, naming conventions, and readability guidelines.
  • Use Case: after a feature, bug fix, or refactor, run the reviewer to generate a prioritized feedback report for the next PR.

Quick Start

Run the code-reviewer on your current git working tree to generate a findings report for the latest changes.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I check my git diff for security vulnerabilities and code quality issues?

To check a git diff for security vulnerabilities and code quality issues, run the code reviewer on your working tree to surface risks and generate a prioritized feedback report based on a deterministic checklist.

What is the best way to automate pull request code reviews for maintainability?

Automating pull request code reviews for maintainability is done by applying static analysis to recent feature or refactor changes, enforcing project patterns and naming conventions to produce structured feedback for developers.

Can I use automated static analysis on any repository branch?

Yes, you can use static analysis on any repository because the reviewer applies to diffs across features, fixes, or refactors, providing actionable feedback regardless of the branch context.

How does static analysis identify security risks in recent code changes?

Static analysis identifies security risks in recent code changes by examining the latest git diff against a deterministic checklist, surfacing potential vulnerabilities and advising mitigations in a reportable format.

Does the code review checklist work for CI workflows?

Yes, the code review checklist works for CI workflows by providing a structured, reportable review output that can be consumed by developers and automated continuous integration processes.

When should I run an automated code reviewer on my working tree?

You should run an automated code reviewer on your working tree after completing a feature, bug fix, or refactor to generate a findings report for the next pull request and reduce manual review time.