skills.rest
decocms
decocmsOFFICIAL
Explore all skills by this author →
Website𝕏@deco_cmsGitHub

review-pr

Review git diffs against main for correctness, security, and performance issues.

396|51|Updated Mar 14, 2025
Search Tags:#testing#architecture#code review#pull request#security review#git diff#remediation plan
One-click install
npx skills add https://github.com/decocms/studio --skill review-pr-decocms
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/decocms/studio/tree/main/.claude/skills/review-pr
Command: npx skills add https://github.com/decocms/studio --skill review-pr-decocms

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you evaluate a branch’s code changes before merging by organizing a structured, multi-angle review of the git diff against main. It reduces the chance of shipping bugs, security issues, performance regressions, and incomplete work.

Core Features & Use Cases

  • Multi-perspective critique: Reviews the diff from duplication, correctness, security, performance, testing, architecture, and scope angles.
  • Parallel subagent workflow: Spawns independent critics so issues are found faster and with less bias.
  • Actionable remediation planning: Converts findings into a prioritized plan with blockers, important fixes, and optional follow-ups.
  • Use Case: Before opening a pull request, ask it to review your branch so you get a concise list of issues and a clear fix plan.

Quick Start

Ask the skill to review the current branch against main and return a prioritized remediation plan.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I review a git diff for security and correctness before a pull request?▼

Reviewing a git diff for security and correctness before a pull request requires analyzing branch changes against main to identify performance, duplication, and scope issues, producing a prioritized remediation plan to fix blockers before merging.

What is the best way to generate a remediation plan from a git diff?▼

Generating a remediation plan from a git diff involves evaluating branch changes against main from multiple perspectives like architecture and testing, then converting the findings into a prioritized list of blockers, important fixes, and optional follow-ups.

How do you check for performance regressions and scope issues in a pre-merge code review?▼

Checking for performance regressions and scope issues in a pre-merge code review requires evaluating the git diff against main, spawning independent critics to find duplication and architecture problems, and returning a prioritized list of required fixes.

Can I automate branch critique and post-implementation validation using a git diff?▼

Automating branch critique and post-implementation validation using a git diff is possible by accessing the repository diff and commit history to evaluate changes against main, producing a structured list of correctness and testing issues to resolve.

Does a multi-perspective code review require access to the entire commit history?▼

A multi-perspective code review requires access to the repository diff, changed files, and commit history to effectively identify correctness, security, and architecture issues, ensuring a comprehensive prioritized remediation plan for the branch.

Related Skills

Explore More Software Engineering Skills→
helderbertohelderberto
114

ship

Stage all Git changes, generate a commit message, and push to the current branch.

Community
Basic
avvaleavvale

commit-pr

Commit changes, push to a feature branch, and create a GitHub Pull Request.

Official
Advanced
EotelEotel

refactor-clean

Identify and remove dead code with test verification and rollback.

Community
Intermediate
mgratzermgratzer
65

forge-reflect-pr

Review the current PR branch for refactoring, test, and documentation gaps.

Community
Advanced