skills.rest
mrclrchtr
mrclrchtrCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

review-changes

Identify actionable issues in diffs, PRs, commits, files, and architecture docs.

8|1|Updated Feb 14, 2026
Search Tags:#verification#review#conventions#diff#code-review#pull-request#findings
One-click install
npx skills add https://github.com/mrclrchtr/skills --skill review-changes-mrclrchtr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-changes
Source: https://github.com/mrclrchtr/skills/tree/main/skills/review-changes
Command: npx skills add https://github.com/mrclrchtr/skills --skill review-changes-mrclrchtr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured guidance to identify and report actionable issues across code diffs, PRs, commits, and architecture documents, reducing review toil and improving quality.

Core Features & Use Cases

  • Deterministic review targets across diffs, PRs, commits, and design docs.
  • Step-by-step guidance to read changes, enforce conventions, and surface findings.
  • Use case: during a PR review, automatically surface P0–P3 findings with suggested fixes and a final verdict.

Quick Start

Provide a diff, PR URL, or target file for analysis to generate a structured findings report.

Frequently Asked Questions about review-changes

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

FAQPage Schema
How do I automate code review findings for a pull request?▼

You can automate code-review findings by providing a diff, PR URL, or target file to generate a structured report with a verdict, prioritized P0–P3 issues, and a concrete remediation path.

What is the best way to identify actionable issues in a large multi-file diff?▼

Identifying actionable issues in a large diff requires reading changes, enforcing conventions, and surfacing prioritized findings. This approach applies structured guidance to both small patches and large diffs across multiple files.

Can I review architecture documents for convention violations using automated findings?▼

Yes, you can review architecture documents for convention violations. The review process targets design docs alongside diffs and commits to surface actionable issues and guide concrete remediation.

How does a structured code review report improve remediation speed?▼

A structured code-review report improves remediation speed by providing a final verdict, prioritized P0–P3 issues, and suggested fixes. This reduces review toil by focusing on actionable findings.

Do I need to install dependencies to generate findings from code changes?▼

No dependencies are required to generate findings from code changes. You can provide a diff, PR URL, or target file directly for analysis without installing external packages.

When should I avoid automated code review for diffs?▼

Avoid automated code review for diffs when you need subjective feedback on overall architecture, as this process focuses on deterministic convention enforcement and surfacing concrete, actionable issues for remediation.

Related Skills

Explore More Software Engineering Skills→
DatTran26DatTran26

ck:code-review

Review code changes for defects and security issues with adversarial testing.

Community
Advanced
przbaduprzbadu
1

pr-review

Review GitHub pull requests and fix Copilot comments using parallel agents.

Community
Advanced
AnveioAnveio
1

task-pull-request

Automate GitHub pull request creation, reviews, feedback, and merges via gh CLI.

Community
Intermediate
tapanshahtapanshah

code-reviewer

Analyze pull requests for complexity, risk, and code quality issues.

Community
Advanced