code-review

Analyze git diffs and generate structured Markdown review summaries.

1|Updated Feb 1, 2026

Search Tags:#automation #GitHub #PR #code-review #rules #diffs #code-segmentation

Ready to run

npx skills add https://github.com/gestrich/PRRadar --skill code-review-gestrich

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/gestrich/PRRadar/tree/main/docs
Command: npx skills add https://github.com/gestrich/PRRadar --skill code-review-gestrich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the tedious process of reviewing code changes by analyzing git diffs or PR diffs and producing a structured summary of findings.

Core Features & Use Cases

Segment diffs into logical code units (methods, declarations, etc.), enabling focused rule checks per unit.
Apply rule-based reviews to each segment and generate a consolidated review summary for PRs or commits.
Use cases include pre-merge quality checks, documentation of changes, and compliance-friendly code reviews.

Quick Start

Use the code-review skill to analyze a PR with changes to multiple files and generate a review summary.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I automate pull request code reviews using diffs?▼

Automate pull request code reviews by analyzing git diffs to segment files into logical units, applying rule-based checks to each segment, and generating a structured Markdown summary with findings and documentation links.

How does code segmentation work for automated rule-based checks?▼

Code segmentation works by breaking down file diffs into logical units like methods and declarations, enabling focused rule-based checks per segment rather than reviewing entire files, which produces granular per-segment results.

Can I review local git commits or do I need a GitHub PR?▼

You can review both local git commits and GitHub pull requests. The skill reads diffs via GitHub CLI or local git, allowing you to analyze changes and generate structured review summaries in either context.

What's the best way to run pre-merge quality checks on multiple files?▼

Run pre-merge quality checks by using automated diff analysis to segment multiple changed files into logical units, apply rule-based evaluations via subagents, and consolidate findings into a single Markdown review summary.

Does the code review skill require GitHub CLI to function?▼

GitHub CLI is not strictly required. The skill reads diffs via GitHub CLI or local git, so you can execute rule-based reviews and generate structured summaries using local repository history instead of pulling from GitHub.

What limitations exist when segmenting diffs into logical code units?▼

Segmenting diffs into logical code units relies on parsing structural elements like methods and declarations. Complex or minified code with unclear structural boundaries may limit segmentation accuracy and affect rule-based check results.