skills.rest
rajivpant
rajivpantCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

synthesis-pr-review

Evaluate pull request changes for correctness, regression risk, and integration readiness.

15|2|Updated Mar 17, 2026
Search Tags:#code review#pull request#security#integration#root cause analysis#delta review#regression risk
One-click install
npx skills add https://github.com/rajivpant/synthesis-skills --skill synthesis-pr-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: synthesis-pr-review
Source: https://github.com/rajivpant/synthesis-skills/tree/main/synthesis-pr-review
Command: npx skills add https://github.com/rajivpant/synthesis-skills --skill synthesis-pr-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR changes can introduce regressions, incomplete fixes, or integration surprises that break behavior or create technical debt; this Skill frames a repeatable delta-review process to surface scope mismatches, root-cause errors, and integration risks before merge.

Core Features & Use Cases

  • Delta-focused checklist for scope, root-cause validation, regression risk, architectural consistency, completeness, security, and data integrity.
  • Severity-tiered feedback template (Must Fix / Should Fix / Consider / Nit) and a lead integration format for clear actionable guidance.
  • Integration guidance and verification including adopt-and-adapt workflows, post-merge verification steps, and when to escalate to full integration branches.
  • Use Case: Peer or lead reviewer evaluating a bugfix or feature PR to decide whether to approve, request changes, or adapt before merging.

Quick Start

Read the PR description and diff, evaluate scope, regressions, root cause, completeness, and produce a verdict with Must Fix, Should Fix, Consider, and Nit sections.

Frequently Asked Questions about synthesis-pr-review

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

FAQPage Schema
How do I review a pull request for regression risk and integration readiness?▼

To review a pull request for regression risk and integration readiness, evaluate the delta diff against a checklist covering scope, root-cause validity, completeness, security, and data integrity. This process surfaces integration surprises and scope mismatches before merging.

What is the best way to structure pull request feedback to prevent technical debt?▼

The best way to structure pull request feedback is using a severity-tiered template with Must Fix, Should Fix, Consider, and Nit sections. This format provides clear, actionable guidance for peer reviewers and lead integrators.

How does a delta-focused code review validate root cause fixes?▼

A delta-focused code review validates root cause fixes by analyzing the PR diff to ensure the changes address the actual underlying issue rather than masking symptoms, preventing incomplete fixes and future regressions.

Can I use a checklist-based PR review for GitHub-style repositories?▼

Yes, you can apply checklist-based PR reviews to single-PR deltas in GitHub-style repositories. This workflow supports peer review, lead integration, and adopt-and-adapt workflows by verifying scope, security, and data integrity.

What steps should I follow for post-merge verification after a code review?▼

For post-merge verification after a code review, follow integration guidance steps including verifying scope completeness, data integrity, and regression risk, and escalate to full integration branches if adopt-and-adapt workflows reveal further issues.

When should I escalate a pull request to a full integration branch?▼

You should escalate a pull request to a full integration branch when the delta review uncovers high regression risk, scope mismatches, or integration surprises that cannot be resolved through a standard single-PR peer review.

Related Skills

Explore More Software Engineering Skills→
man-groupman-group
2.5k

review-pr

Review ArcticDB pull requests and post deduplicated inline comments.

Official
Advanced
lvlup-swlvlup-sw
33

cleanup

Verify merged PRs, backfill metadata, and prune git worktrees and branches.

Official
Advanced
ayeshakhalid192007-devayeshakhalid192007-dev
1

code-analyzer

Analyze codebases for security, performance, and maintainability issues across files and dependencies.

Community
Advanced
ajsai47ajsai47
11

review

Analyze git diffs for SQL injection, race conditions, and shell injection risks.

Community
Advanced