review

Name: review
Availability: InStock
Author: ligianehua

Analyze git diffs for SQL safety, LLM trust boundaries, and structural defects.

Updated Mar 30, 2026

Search Tags:#workflow #qa #review #diff #code-quality #plan #pr

Ready to run

npx skills add https://github.com/ligianehua/Gstack --skill review-ligianehua

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/ligianehua/Gstack/tree/main/review
Command: npx skills add https://github.com/ligianehua/Gstack --skill review-ligianehua

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewing code changes before merging is critical but often misses structural issues in diffs, such as SQL safety gaps, LLM prompt safety boundaries, and potential side effects that can escape lightweight checks. This Skill automates and guides PR reviews, surfacing these risks early and suggesting concrete remediation.

Core Features & Use Cases

Surface SQL safety risks, LLM trust boundary violations, and conditional side effects in diffs.
Proactively suggest when a merge could be risky and provide remediation steps.
Integrate with pre-landing review workflows to improve code quality and reduce post-merge incidents.

Quick Start

Describe the PR you want to review and run /review to generate a pre-landing PR audit.

Frequently Asked Questions about review

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

FAQPage Schema

How do I perform a pre-landing code review on a git diff?▼

A pre-landing PR review analyzes the git diff against the base branch to surface SQL safety issues, LLM trust boundary violations, and structural defects, providing actionable remediation suggestions to ensure clean code changes.

What are common SQL safety and LLM trust boundary risks found in PR diffs?▼

Common PR diff risks include SQL safety gaps that can cause data leaks, LLM prompt safety boundary violations from untrusted inputs, and conditional side effects that escape lightweight checks and cause post-merge incidents.

How do I automate checks for structural defects in code changes before merging?▼

Automate checks for structural defects by integrating a pre-landing review workflow that analyzes diffs against the base branch, categorizing findings of SQL safety and LLM trust boundary violations to guide remediation.

Do I need contextual plan data to review a PR for code quality?▼

Yes, reviewing a PR for code quality requires access to the git diff, the base branch name, and contextual plan data to accurately categorize findings and guide the remediation workflow for structural defects.

What is the best way to surface risky merges and get remediation steps for code reviews?▼

The best way to surface risky merges is to run a pre-landing PR audit that proactively identifies structural defects in diffs and suggests concrete remediation steps to improve code quality before integration.