gstack-review

Analyze pull request code diffs for structural issues, scope creep, and test coverage.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the review process for pull requests by analyzing code diffs for structural issues, scope drift, test coverage, and design consistency, ensuring high-quality code before merging.

Core Features & Use Cases

  • Code Diff Analysis: Detects scope creep, missing features, and regressions by comparing changes against the base branch.
  • Checklist Validation: Reads predefined review checklists and applies them to code changes to identify issues.
  • Coverage Assessment: Analyzes test coverage for new or modified code paths, and suggests or generates missing tests.
  • Design Review: Validates frontend code changes against design principles, standards, and existing design docs if available.
  • Request Optimization: Guides reviewers with specific questions about scope, safety, and implementation quality, improving review thoroughness.

Quick Start

Use the gstack review skill to analyze the current PR against the target branch, checking for code quality issues, scope drift, and test coverage gaps.

Frequently Asked Questions about gstack-review

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

FAQPage Schema
How do I automate pull request code review for scope creep and test coverage?

Automating pull request code review involves analyzing code diffs to detect structural issues, scope creep, and missing test coverage. This pre-merge process applies review checklists to flag potential problems and ensure design consistency.

What is the best way to validate design consistency in a pre-merge code review?

Validating design consistency in a pre-merge review requires analyzing frontend code changes against predefined design principles, standards, and existing design docs. This process flags potential design deviations early in the collaborative development cycle.

How do I assess test completeness for new code paths in a pull request?

Assess test completeness for new code paths by analyzing test coverage specifically for modified code sections within the pull request diff. The review process identifies missing tests and suggests or generates them to ensure comprehensive coverage.

Can I use a review checklist to guide automated code diff analysis?

Yes, you can use a predefined review checklist to guide automated code diff analysis. The system reads your checklist and systematically applies its criteria to the code changes, identifying structural issues and flagging potential problems during the pre-merge review.

Does automated PR pre-review work without integrating external testing frameworks?

Automated PR pre-review works by analyzing pull request code differences directly against the target branch. It assesses test coverage and flags missing tests by examining the code diff itself, ensuring code quality without requiring external testing framework integrations.