review

Analyze pull request diffs for structural safety, correctness, and completeness issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill facilitates thorough and structured review of pull requests by analyzing code diffs for structural, safety, and quality issues, reducing review time and catching potential risks early.

Core Features & Use Cases

  • Structural Diff Analysis: Examines code changes against best practices and safety guidelines, focusing on SQL safety, concurrency, and trust boundaries for LLM outputs.
  • Coverage & Testing Gaps: Identifies untested code paths, missing edge case tests, and regression points requiring attention.
  • Workflow Optimization: Guides users through manual review, suggesting mechanical fixes, flagging issues, and prioritizing critical problems for fixing or escalation.
  • Use Case: A developer submits a large feature PR. This Skill analyzes the diff for security vulnerabilities, code quality, and test coverage gaps, providing clear issues for quick fixes.

Quick Start

Run /review to analyze the current branch's diff against the base branch, highlighting critical issues like SQL safety, race conditions, and untested code paths, then generate fixes or questions for ambiguous problems.

Frequently Asked Questions about review

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

FAQPage Schema
How do I analyze code diffs for security issues and testing gaps in a pull request?

Analyzing code diffs for security issues and testing gaps in a pull request involves examining structural changes against best practices to identify SQL safety risks, concurrency problems, and untested code paths. This structural review process highlights critical issues requiring fixes.

What is structural diff analysis and how does it improve code review?

Structural diff analysis improves code review by examining code changes against safety guidelines and best practices. It focuses on identifying SQL safety vulnerabilities, concurrency race conditions, and trust boundary issues for LLM outputs to catch potential risks early.

Do I need git and gh installed to run automated pull request reviews?

Yes, you need git and gh installed to run automated pull request reviews, along with jq. These dependencies allow the review process to fetch branch differences and execute structural analysis directly within your development environment.

What's the best way to find untested code paths and missing edge case tests in a feature branch?

The best way to find untested code paths and missing edge case tests in a feature branch is to run a comprehensive structural review. It identifies regression points and coverage gaps by analyzing the pull request diff against established testing requirements.

Does automated code review work for large feature pull requests with concurrency problems?

Automated code review works effectively for large feature pull requests by analyzing the diff for concurrency problems and security vulnerabilities. It prioritizes critical issues and generates actionable recommendations or mechanical fixes for quick resolution.

Can I generate fixes for SQL safety issues flagged during a pull request review?

Yes, you can generate fixes for SQL safety issues flagged during a pull request review. The structural analysis workflow suggests mechanical fixes for identified vulnerabilities and provides clear questions for ambiguous problems requiring further inspection.