review

Name: review
Availability: InStock
Author: nocnoc

Analyze diffs against the base branch for SQL safety and trust boundary risks.

Updated Mar 21, 2026

Search Tags:#automation #review #pr-review #diff-analysis #sql-safety #llm-trust

Ready to run

npx skills add https://github.com/nocnocgroup/gstack --skill review-nocnocgroup

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR review is automated to analyze diffs against the base branch for SQL safety, LLM trust boundary violations, and other structural issues, helping teams catch issues before merging.

Core Features & Use Cases

Analyzes diffs against the base branch for SQL safety, LLM trust boundary violations, and conditional side effects.
Proactively suggests when changes may impact merging, deployment, or production risk.
Use Case: When reviewing a pull request, run this skill to surface potential issues before merge and guide remediation.

Quick Start

Invoke this skill on a PR to scan the diff against the base branch and surface SQL safety issues, LLM trust violations, and potential side effects.

Frequently Asked Questions about review

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

FAQPage Schema

How do I automate pre-landing PR review for SQL safety risks?▼

Automated pre-landing PR review analyzes code diffs against the base branch to detect SQL safety risks before merge. It surfaces actionable findings related to unsafe queries and potential side effects to guide remediation.

What is an LLM trust boundary violation in a pull request?▼

An LLM trust boundary violation occurs when code changes improperly handle trust limits around large language model integrations. Pre-landing diff analysis identifies these violations alongside SQL safety risks to prevent unintended side effects.

How do I scan a diff against the base branch for unintended side effects?▼

Scanning a diff against the base branch for unintended side effects requires analyzing the changed code structure. This review process identifies conditional side effects, LLM trust violations, and SQL safety issues prior to merging.

Can I use diff analysis to check LLM trust boundaries before merging?▼

Yes, diff analysis can check LLM trust boundaries before merging by comparing pull request changes against the base branch. This surfaces violations and structural issues to mitigate production risk prior to deployment.

What is the best way to surface actionable findings in a pre-landing PR review?▼

The best way to surface actionable findings in a pre-landing PR review is to analyze diffs for SQL safety and LLM trust violations. This approach proactively identifies potential side effects and deployment risks before code merges.