review-changes

Analyze feature branch changes against the default branch and report issues by severity.

1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/Artmann/review-changes --skill review-changes-artmann
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-changes
Source: https://github.com/Artmann/review-changes/tree/main/skills/review-changes
Command: npx skills add https://github.com/Artmann/review-changes --skill review-changes-artmann

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps software teams quickly identify issues in changes proposed for merge by automatically comparing a feature branch against the repository's default branch (main/master), classifying findings by severity, and suggesting actionable fixes.

Core Features & Use Cases

  • Compare differences between the current branch and the default branch to surface regressions and potential defects.
  • Automatically categorize findings into Critical, Major, and Minor with concrete remediation guidance.
  • Support both PR-based reviews (via PR number or URL) and local-branch audits, using your existing git and GitHub tooling.

Quick Start

Prompt your assistant: "Review the changes in PR #123 against main" or "Audit the current branch for issues before merge".

Frequently Asked Questions about review-changes

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

FAQPage Schema
How do I review code changes before merge using a pull request?

You can review code changes by comparing a feature branch against the default branch. The skill fetches PR data via GitHub CLI, computes diffs, and reports security, correctness, and maintainability issues categorized by severity.

Can I audit a local git branch for issues before opening a pull request?

Yes, you can audit a local git branch for issues before a merge. The skill analyzes local branch differences against the default branch and applies structured guidelines to detect potential defects and provide remediation guidance.

Do I need GitHub CLI to analyze branch diffs for code quality?

Yes, you need both git and GitHub CLI (gh) installed to analyze branch diffs. The tool requires these dependencies to fetch pull request data, compute differences between branches, and present actionable feedback.

What is the best way to classify code review findings by severity?

The best way to classify code review findings is to automatically categorize them into Critical, Major, and Minor levels. This approach surfaces regressions and provides concrete remediation guidance for each severity tier.

Does this code review tool check for security and maintainability concerns?

Yes, the code review tool checks for security, correctness, and maintainability concerns. It applies structured guidelines to the computed diff between branches to detect these issues and suggest actionable fixes before merging.