skills.rest
AlexandreLab
AlexandreLabCOMMUNITY
Explore all skills by this author →
GitHub

gstack-review

Analyze pull request diffs for SQL safety and trust boundary risks.

Updated Apr 12, 2026
Search Tags:#pr#code-review#risk-analysis#trust-boundaries#diff-analysis#sql-safety
One-click install
npx skills add https://github.com/AlexandreLab/dotfiles --skill gstack-review-alexandrelab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-review
Source: https://github.com/AlexandreLab/dotfiles/tree/main/claude/skills/gstack-review
Command: npx skills add https://github.com/AlexandreLab/dotfiles --skill gstack-review-alexandrelab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly and safely review code changes by analyzing the diff against the base branch for SQL safety issues, LLM trust boundary violations, and potential side effects, helping teams catch structural issues before merging.

Core Features & Use Cases

  • Diff analysis for PR reviews: Assess the changes against the base branch to surface potential risks, including data access patterns and trust boundary concerns.
  • Proactive merge checks: Suggests checks and guardrails when a PR is about to land, reducing downstream surprises.
  • Plan integration: Fits into pre-landing review workflows and supports large codebases where manual review is expensive.

Quick Start

Provide Claude with the PR diff against the base branch to perform a pre-landing PR review.

Frequently Asked Questions about gstack-review

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

FAQPage Schema
How do I review a PR diff for SQL safety and trust boundary violations?▼

Pre-landing PR review identifies risky changes by analyzing the diff against the base branch to validate SQL safety, detect LLM trust boundary violations, and surface unintended side effects before merging.

What is diff analysis for code reviews?▼

Diff analysis for code reviews assesses pull request changes against the base branch to surface potential risks, including data access patterns and trust boundary concerns, ensuring alignment with project safety constraints.

Can I use pre-landing review to suggest merge-time checks?▼

Yes, pre-landing review can proactively suggest merge-time checks and guardrails when a pull request is about to land, reducing downstream surprises by validating structural changes and risk areas.

How do I check my pull request for unintended side effects before merging?▼

You can check a pull request for unintended side effects by providing the PR diff against the base branch for analysis, which validates structural changes and identifies potential risk areas before landing.

Does this code review approach work for large codebases where manual review is expensive?▼

Yes, this diff analysis approach fits into pre-landing review workflows and supports large codebases where manual review is expensive by quickly validating data access patterns and structural changes.

What is the best way to validate data access patterns in a pull request?▼

The best way to validate data access patterns in a pull request is to analyze the diff against the base branch, checking for SQL safety issues and ensuring changes align with project standards and safety constraints.

Related Skills

Explore More Software Engineering Skills→
jm199seojm199seo

review

Analyze pull request diffs against the base branch for structural issues.

Community
Advanced
HomericIntelligenceHomericIntelligence
11

mojo-type-safety

Enforce Mojo type-safety rules with explicit annotations and trait constraints.

Official
Advanced
aporto-techaporto-tech

gstack-review

Analyze code diffs for SQL safety and LLM trust boundary violations.

Official
Advanced
KakarottooooKakarottoooo

review

Analyze feature branch diffs for SQL safety and trust boundary issues.

Community
Advanced