review

Audit diffs for SQL safety, trust boundary violations, and side effects.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit the diff for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues before merging.

Core Features & Use Cases

  • Comprehensive diff analysis for SQL safety, LLM trust boundaries, and side-effect risk before landing code.
  • Proactively suggests when the user is about to merge or land changes.
  • Integrates with gstack's plan-mode workflow to guide planning and decision-making during reviews.

Quick Start

Invoke the review skill on a pending PR to automatically analyze the diff and surface actionable items before merge.

Frequently Asked Questions about review

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

FAQPage Schema
How do I run a pre-landing PR review for SQL safety and side effects?

Pre-landing PR review analyzes your diff for structural issues like SQL safety and conditional side effects. It identifies risks and provides clear gating recommendations to help decide whether to merge the code changes.

What is an LLM trust boundary violation in a code diff?

An LLM trust boundary violation happens when untrusted model inputs cross security perimeters without proper validation. The PR review process detects these boundary issues in the diff to prevent unintended side effects before merge.

Can I use this review skill with plan-mode workflows?

Yes, the review skill integrates with gstack's plan-mode workflow to guide planning and decision-making during reviews. It surfaces actionable items and gating recommendations for pending PRs within the planning environment.

Does the pre-landing review require any external dependencies or tools?

No external dependencies are required to run the pre-landing review. The skill operates independently to analyze the diff and identify structural issues like SQL safety and LLM trust boundary violations before merging.

What's the best way to identify conditional side effects before merging code?

The best way to identify conditional side effects is auditing the diff before landing code. This skill proactively analyzes structural issues and provides clear gating recommendations to help decide whether to merge.

When do I need to audit a diff for SQL safety and structural issues?

You need to audit a diff for SQL safety when preparing to land or merge code changes. The pre-landing review proactively suggests analysis when you are about to merge, surfacing actionable findings and gating recommendations to prevent structural issues.