gs:review

Automate pull request reviews for SQL injection and trust boundary issues.

34|6|Updated Apr 19, 2026

Search Tags:#code review #PR review #SQL safety #pre-landing review #LLM trust boundary

Ready to run

npx skills add https://github.com/thanh-abaii/gstack-windows-port --skill gs-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gs:review
Source: https://github.com/thanh-abaii/gstack-windows-port/tree/main/skills/gstack-review
Command: npx skills add https://github.com/thanh-abaii/gstack-windows-port --skill gs-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Read, Edit, Write, Grep, Glob, Agent, AskUserQuestion, WebSearch, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides automated pre-landing PR reviews, identifying potential SQL safety issues, trust boundary violations, conditional side effects, and other structural problems before code merges.

Core Features & Use Cases

Automated PR Review: Analyzes the diff against the base branch for SQL safety, LLM trust boundary violations, and other structural issues.
Conditional Side Effects: Flags potential side effects from code changes.
Use Case: When you are asked to "review this PR", "code review", or "pre-landing review", use the gs:review skill to automatically check for issues before merging.

Quick Start

Run the /gs:review command to automatically review the changes in your current pull request.

Frequently Asked Questions about gs:review

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

FAQPage Schema

How do I automate PR review for SQL injection risks before merging?▼

You can automate PR review for SQL injection risks by running a pre-landing review that analyzes pull request diffs against the base branch. This detects SQL safety issues and structural problems before code merges.

What is an LLM trust boundary violation in code review?▼

An LLM trust boundary violation occurs when untrusted data crosses into trusted execution zones without proper validation. Automated code review detects these violations by analyzing structural changes in pull request diffs.

How do I check for conditional side effects in pull request changes?▼

To check for conditional side effects in pull request changes, run an automated pre-landing review. It analyzes code diffs to flag potential side effects and structural issues before the code merges into the base branch.

Does automated code review work with Python and PowerShell repositories?▼

Yes, automated code review supports Python and PowerShell repositories. It identifies SQL injection risks, trust boundary violations, and structural problems within these codebases during the pull request review process.

Can I use Bash and Grep to find structural problems in a PR diff?▼

Yes, the automated PR review utilizes Bash, Grep, Read, and Glob to analyze repository changes. These dependencies enable the skill to search and evaluate code diffs for SQL safety and structural problems.

What are the limitations of automating pre-landing code reviews?▼

Automating pre-landing code reviews requires multiple dependencies including Bash, Read, Edit, Write, Grep, Glob, Agent, AskUserQuestion, and WebSearch. Limitations include relying on these tools to detect complex SQL safety and trust boundary issues.