review

Analyze diffs against the base branch for SQL safety and trust boundary issues.

43|7|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/lucas-flatwhite/gstack-ko --skill review-lucas-flatwhite
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/lucas-flatwhite/gstack-ko/tree/main/review
Command: npx skills add https://github.com/lucas-flatwhite/gstack-ko --skill review-lucas-flatwhite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a manual pre-landing PR review workflow that analyzes the current diff against the base branch to surface risks that tests often miss, including SQL safety, LLM trust boundaries, conditional side effects, and structural issues.

Core Features & Use Cases

  • Guides reviewers through a two-pass, risk-focused review process.
  • Checks for SQL safety, LLM trust boundary violations, boundary conditions, and potential side effects.
  • Provides a structured plan and notes when to escalate or run additional checks, improving merge safety.

Quick Start

Use /review to start a pre-landing PR review on the current branch.

Frequently Asked Questions about review

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

FAQPage Schema
How do I do a pre-landing PR review to catch SQL safety and LLM trust boundary issues?

A pre-landing PR review analyzes your current diff against the base branch to surface SQL safety issues, LLM trust boundary violations, and conditional side effects that tests often miss before merging.

What is a risk-focused PR review process?

A risk-focused PR review guides reviewers through a two-pass assessment of the diff, proactively checking for SQL safety, boundary conditions, and side effects to catch structural issues early.

How can I check my diff for conditional side effects before merging?

You can check your diff for conditional side effects by running a structured pre-landing review that surfaces risks often missed by tests, enforcing best practices before the code merges.

Does manual PR review work for identifying LLM trust boundary violations?

Yes, manual PR review works for identifying LLM trust boundary violations by analyzing the current diff against the base branch and guiding reviewers through a complete, risk-focused assessment.

When do I need to escalate issues found during a pre-landing code review?

You need to escalate issues during a pre-landing code review when the structured assessment identifies high-risk SQL safety problems or LLM trust boundary violations that require additional checks.

What is the best way to enforce merge safety for structural issues in a diff?

The best way to enforce merge safety is using a structured review checklist that proactively evaluates the diff for structural issues and provides clear escalation paths before landing code.