code-change-review

Analyze git diffs to provide structured code review feedback.

Updated Dec 11, 2025
One-click install
npx skills add https://github.com/maverox/claude-plugins --skill code-change-review-maverox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-change-review
Source: https://github.com/maverox/claude-plugins/tree/main/plugins/software-engineering-suite/skills/code-change-review
Command: npx skills add https://github.com/maverox/claude-plugins --skill code-change-review-maverox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes code changes to surface quality issues, security concerns, and maintainability gaps, providing structured, actionable feedback to streamline code reviews.

Core Features & Use Cases

  • Context Analysis: Understand intent behind diffs and changes by reviewing commit history and modified files.
  • Comprehensive Review: Evaluate correctness, security, performance, and style, and propose concrete fixes.
  • Feedback & Reporting: Produce structured feedback sections with line-number references and suggested improvements for quick fixes.

Quick Start

Review the latest diff and provide structured feedback with actionable improvements.

Frequently Asked Questions about code-change-review

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

FAQPage Schema
How do I get structured feedback on a git diff for code quality and security?

Structured feedback on a git diff requires modified files and repository context to evaluate correctness, security, performance, and maintainability. The analysis returns actionable recommendations with line-number references for quick fixes.

What is the best way to automate code review for correctness and maintainability?

Automating code review for correctness and maintainability involves analyzing diffs against commit history and modified files. This approach surfaces quality issues and maintainability gaps, providing structured, actionable feedback to streamline the review process.

Can I use diff analysis across diverse codebases and different programming languages?

Diff analysis applies to diverse codebases across various programming languages. It focuses on universal best practices, security, and performance to identify issues and generate actionable recommendations regardless of the specific language.

How do I review code changes for security concerns and performance issues?

Reviewing code changes for security and performance requires analyzing the intent behind diffs using commit history. The evaluation produces structured feedback sections highlighting security concerns and proposing concrete performance fixes.

Does code review feedback include line-number references for quick fixes?

Yes, code review feedback includes line-number references and suggested improvements. The reporting produces structured feedback sections specifically designed to identify issues and generate actionable recommendations for quick fixes.

What context do I need to provide to analyze a code diff?

Analyzing a code diff requires access to git diffs, modified files, and repository context. This allows the analysis to understand the intent behind changes by reviewing commit history and accurately identify issues.