skills.rest
anilveersingh1308
anilveersingh1308COMMUNITY
Explore all skills by this author →
GitHub

gstack-review

Review pull request diffs for SQL safety and trust-boundary violations.

Updated May 19, 2026
Search Tags:#diff analysis#pr review#merge readiness#security checks#sql safety#pre-landing#llm trust boundary
One-click install
npx skills add https://github.com/anilveersingh1308/copilot-skills --skill gstack-review-anilveersingh1308
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-review
Source: https://github.com/anilveersingh1308/copilot-skills/tree/main/.github/skills/gstack-review
Command: npx skills add https://github.com/anilveersingh1308/copilot-skills --skill gstack-review-anilveersingh1308

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you avoid risky merge mistakes by reviewing a PR diff against the base branch for SQL safety and structural security issues before anything lands.

Core Features & Use Cases

  • Pre-landing PR review: Checks diffs for SQL safety problems, LLM trust-boundary violations, conditional side effects, and other structural issues that commonly cause production incidents.
  • Proactive safety prompting: When you are about to merge or land code changes, it can suggest the review automatically based on your state and request intent.
  • Diff-focused guidance: Uses the “review this PR” style triggers to focus specifically on what changed and why it might be unsafe.

Quick Start

Use the gstack-review skill by asking: review this PR for sql safety and trust boundary issues before merging.

Frequently Asked Questions about gstack-review

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

FAQPage Schema
How do I check a pull request diff for SQL safety and LLM trust-boundary violations before merging?▼

Pre-landing PR review analyzes your pull request diff against the base branch to detect SQL safety failures, LLM trust-boundary violations, and risky structural issues before code merge.

What is pre-landing code review and when do I need it?▼

Pre-landing code review is a deterministic analysis of unmerged changes to identify conditional side effects and structural risks. You need it before landing code to prevent production incidents caused by unsafe diffs.

How do I run a pre-landing analysis on my PR to ensure merge readiness?▼

To run a pre-landing analysis, trigger a review by requesting to check your diff before merging. The system applies deterministic review behavior, plan-mode handling, and structured user confirmation gates to verify merge readiness.

Does pre-landing PR review work with LLM-generated code changes?▼

Yes, pre-landing PR review explicitly checks for LLM trust-boundary violations from generated outputs. It applies deterministic review behavior to ensure safe operational steps when analyzing LLM-generated code changes.

What is the best way to detect risky structural issues in a diff before landing code?▼

The best way to detect risky structural issues is a diff-focused pre-landing review against the base branch. This approach identifies conditional side effects and structural problems that commonly cause production incidents before merge.

What are the limitations of automated pre-landing SQL safety checks?▼

Automated pre-landing SQL safety checks are limited to analyzing the pull request diff against the base branch. They require deterministic review behavior and structured user confirmation gates, meaning they focus on code changes rather than runtime database states.

Related Skills

Explore More Software Engineering Skills→
bhianerdbhianerd
1

review

Review pull request diffs for SQL safety, LLM trust boundaries, and concurrency hazards.

Community
Advanced
zz8011zz8011

review

Analyze PR diffs for SQL safety, LLM trust boundary violations, and conditional side effects.

Community
Intermediate
lengoctuong2005lengoctuong2005
5

requesting-code-review

Automate pre-commit code review with security scans, tests, and fixes.

Community
Advanced
smarmen86smarmen86

review

Analyze git diffs against base branches for SQL vulnerabilities and code defects.

Community
Advanced