review

Analyze pull request diffs for structural issues and missing tests.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/mgher668/surf-ai --skill review-mgher668
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/mgher668/surf-ai/tree/main/.agents/skills/gstack/review
Command: npx skills add https://github.com/mgher668/surf-ai --skill review-mgher668

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prs are easy to merge when changes look small but hide risks. This guide helps teams catch structural issues in a PR before merging by analyzing the diff, aligning with plan intent, and surfacing gaps in testing and requirements.

Core Features & Use Cases

  • Diff analysis for scope drift and architectural concerns.
  • Plan and TODOS alignment checks to ensure planned work was delivered.
  • Actionable recommendations and risk flags that guide when to fix or discuss changes.

Quick Start

Run the /review workflow on the current PR to analyze the diff and surface issues before landing.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a pull request for scope drift before merging?

To review a pull request for scope drift, you can analyze the current PR diff against your planned scope and TODOS to surface structural issues, missing tests, and architectural concerns before landing the code.

What is the best way to catch missing tests in a pre-landing PR review?

The best way to catch missing tests in a pre-landing PR review is to inspect the diff and align it with plan intent, which surfaces gaps in testing and requirements alongside actionable risk flags.

Can I use automated diff analysis for both GitHub and GitLab workflows?

Yes, automated diff analysis applies to pre-landing PR reviews across both GitHub and GitLab workflows, focusing on intent alignment, risk areas, and actionable findings to ensure reliable merges.

How does plan alignment help identify structural issues in a code diff?

Plan alignment compares the actual code diff against the planned scope and TODOS to detect structural issues and scope drift, reporting severity, suggested fixes, and next steps for resolution.

What actionable recommendations does a pre-landing code review provide?

A pre-landing code review provides actionable recommendations by inspecting the diff to report severity, suggest fixes, and guide when to discuss changes, ensuring planned work is delivered reliably.