review

Review branch diffs for scope drift and missing requirements.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/viraatdas/vstack --skill review-viraatdas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/viraatdas/vstack/tree/main/review
Command: npx skills add https://github.com/viraatdas/vstack --skill review-viraatdas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diff-based pre-landing PR reviewer that flags structural issues not caught by tests.

Core Features & Use Cases

  • Detect scope drift between the feature branch and base branch
  • Flag missing requirements and potential pre-landing blockers
  • Produce a structured GSTACK review report with actionable items for faster shipping

Quick Start

Run the /review workflow on your current branch to generate a GSTACK review report.

Frequently Asked Questions about review

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

FAQPage Schema
How do I detect scope drift in a feature branch before merging?

You can detect scope drift by running a diff-based pre-landing review on your current branch against the base branch. This flags structural issues, missing requirements, and deliverable misalignment that automated tests often miss.

What is a pre-landing PR review and how does it differ from automated testing?

A pre-landing PR review evaluates structural issues and deliverable alignment using branch diffs, whereas automated testing validates code execution. The review classifies findings into statuses like DONE, BLOCKED, or NEEDS_CONTEXT for actionable resolution.

How do I generate a structured review report for my pull request?

Generate a structured review report by running the review workflow on your current local branch. It compares your changes against the base branch and outputs a GSTACK summary with actionable items to speed up safe merging.

Can I automate PR quality checks using local git state?

Yes, PR quality checks can be automated using your local git state. The review process applies diff analysis against the base branch to identify pre-landing blockers and log telemetry without needing external test runners.

Does pre-landing review work without external dependencies or test suites?

Pre-landing review works without external dependencies by relying on local git state and plan-mode tooling. It classifies structural findings internally, meaning no additional test suites or external libraries are required to flag missing requirements.

Why are structural issues missed by tests flagged during a diff review?

Structural issues are missed by tests because tests validate execution behavior, not deliverable alignment. A diff review analyzes the branch changes against base requirements, classifying findings as BLOCKED or NEEDS_CONTEXT to catch these gaps.