skills.rest
aporto-tech
aporto-techOFFICIAL
Explore all skills by this author →
GitHub

gstack-review

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

Updated Jun 4, 2026
Search Tags:#code review#code analysis#SQL safety#pre-landing review#LLM trust boundary
One-click install
npx skills add https://github.com/aporto-tech/aporto-agent-skills --skill gstack-review-aporto-tech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-review
Source: https://github.com/aporto-tech/aporto-agent-skills/tree/main/skills/gstack/review
Command: npx skills add https://github.com/aporto-tech/aporto-agent-skills --skill gstack-review-aporto-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, python, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of code review, identifying potential issues like SQL safety, LLM trust boundary violations, and structural problems before merging or landing code changes.

Core Features & Use Cases

  • Automated Code Review: Analyzes code diffs for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues.
  • Pre-Landing Review: Suggests review when users are about to merge or land code changes.
  • Use Case: When a developer wants to review a pull request before merging it into the main branch, this Skill can be used to automatically check for potential issues.

Quick Start

Run the gstack-review skill on the latest code changes to ensure they meet the necessary standards 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 for SQL safety before merging code changes?▼

To check SQL safety before merging, you can automate code review to analyze code diffs for potential SQL injection risks and structural issues. This pre-landing review process identifies vulnerabilities before code lands in the main branch.

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

An LLM trust boundary violation in code analysis occurs when untrusted model inputs cross security limits without validation. Automated code review detects these violations by analyzing code diffs before changes are merged into the main branch.

How do I automate a pre-landing code review for pull requests?▼

You automate a pre-landing code review by running a script that analyzes code diffs for SQL safety, LLM trust boundary violations, and structural problems. This ensures your pull request meets standards before merging into the main branch.

Do I need git and python to run automated code analysis on diffs?▼

Yes, you need git and python installed to run automated code analysis on diffs. These dependencies are required to access the codebase, generate diffs, and execute the scripts that check for SQL safety and LLM trust boundary violations.

What is the best way to detect conditional side effects in a pull request?▼

The best way to detect conditional side effects is to apply automated diff analysis during pre-merge code review. This approach scans for structural issues and side effects before changes are merged into the main branch.

Related Skills

Explore More Software Engineering Skills→
missdeermissdeer

audit

Review pending git diffs for correctness, security, and style issues.

Community
Intermediate
cwijayasundaracwijayasundara
3

gate

Execute pre-merge quality gate checks with automated code reviews and security checks.

Community
Advanced
GrassHopper42GrassHopper42

health

Compute a weighted composite code quality score from project tools.

Community
Advanced
matteocervellimatteocervelli
25

security-scanner

Scan codebases for secrets, vulnerable dependencies, and insecure patterns.

Community
Advanced