code-review

Analyze code diffs and report evan-workflow rule violations by severity.

2|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/EvanPluchart/kyomu --skill code-review-evanpluchart
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/EvanPluchart/kyomu/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/EvanPluchart/kyomu --skill code-review-evanpluchart

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you quickly analyze modified code and produce a structured list of issues aligned with the evan-workflow rules and conventions, so you can review changes more safely and consistently.

Core Features & Use Cases

  • Diff-based analysis: Reviews unstaged + staged diffs, a specific commit, a commit range, a whole branch diff vs main, or targeted files.
  • Rule and pattern alignment: Detects naming, code style, and evan-workflow patterns by loading the relevant manifests and stack-specific guidelines.
  • Actionable reporting: Classifies findings by severity (CRITIQUE/HAUTE/MOYENNE/BASSE), includes file/line/rule references, and provides correction suggestions and a next-step recommendation.

Quick Start

Run /code-review --branch feature/xxx to analyze the branch diff against main and generate a severity-sorted report of issues to fix.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I generate a code review report from a git diff against a target branch?

Analyzing modified code diffs against conventions generates a severity-sorted report of rule violations. It reviews unstaged, staged, or branch-specific changes, loading relevant manifest rules to classify issues by severity and provide actionable correction suggestions.

Can I review staged and unstaged file changes or do I need a specific commit range?

You can review staged and unstaged changes directly without a specific commit range. The analysis applies to individual commits, commit ranges, full branch diffs versus main, or explicitly targeted files within a software repository.

What is severity classification in static analysis and how does it structure code review findings?

Severity classification in static analysis categorizes detected rule violations into levels like CRITIQUE, HAUTE, MOYENNE, and BASSE. This structures code review findings by prioritizing issues, helping developers address critical security checks and conventions before minor style infractions.

Does this code review tool enforce custom naming conventions and code style patterns?

Yes, the code review tool enforces custom naming conventions and code style patterns. It detects issues by loading relevant manifests and stack-specific guidelines aligned with your established workflow rules before generating the final structured report.

What is the best way to analyze a whole feature branch for security checks and rule violations?

The best way to analyze a whole feature branch is to run a diff against main. This generates a per-file change summary, applies security checks and convention rules, and outputs a severity-sorted report with actionable next-step recommendations.

Why does my static analysis report include a per-file change summary during code review?

Static analysis reports include a per-file change summary to provide context for detected rule violations. Summarizing modified code diffs allows the review process to accurately apply stack-specific style patterns and classify issues by severity.