review

Analyze PR diffs against the base branch for structural issues.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/studyzy/dev-agent-protocol --skill review-studyzy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/studyzy/dev-agent-protocol/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/studyzy/dev-agent-protocol --skill review-studyzy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes the current PR diff against the base branch to surface structural issues and risk areas that tests might miss, enabling safer and higher-quality merges.

Core Features & Use Cases

  • Two-pass pre-landing PR analysis that targets SQL safety, LLM trust boundaries, scope drift, and design-consistency issues.
  • Scope-drift and intent validation by comparing PR messages, TODOS, and commit history against the actual diff.
  • Auto-Fix for mechanical issues, and Ask-User questions for ambiguous or risky changes, with a telemetry trail on completion.
  • Optional design-checks and Greptile triage pathways to strengthen review coverage.

Quick Start

Run the review workflow on your current branch to analyze the diff against the base branch and surface issues.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a PR diff for structural issues tests might miss?

Automated PR review analyzes the current branch diff against the base branch to surface structural problems and risk areas, ensuring safer merges before integration.

What is scope drift detection in a pull request?

Scope drift detection validates intent by comparing PR messages, TODOS, and commit history against the actual code diff to identify unauthorized or misaligned changes.

How does automated PR review handle ambiguous code changes?

The two-pass review workflow applies auto-fixes for mechanical issues and generates Ask-User questions for ambiguous or risky changes, creating a telemetry trail on completion.

Can I analyze SQL safety and LLM trust boundaries in a code diff?

Yes, the pre-landing PR analysis specifically targets SQL safety, LLM trust boundaries, scope drift, and design-consistency issues to strengthen review coverage before merging.

Do I need to read TODOS.md before running a PR review?

Yes, the review workflow requires reading TODOS.md and PR descriptions to validate intent and ensure the code changes align with the project's documented requirements.