skills.rest
adryanmoldokkr32-pixel
adryanmoldokkr32-pixelCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

review

Analyze PR diffs for SQL safety, trust boundary, and side-effect risks.

Updated Apr 12, 2026
Search Tags:#security#quality#review#diff#code-review#pull-request#pre-landing
One-click install
npx skills add https://github.com/adryanmoldokkr32-pixel/gstack --skill review-adryanmoldokkr32-pixel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/adryanmoldokkr32-pixel/gstack/tree/main/review
Command: npx skills add https://github.com/adryanmoldokkr32-pixel/gstack --skill review-adryanmoldokkr32-pixel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR reviews are time-consuming and error-prone. This Skill analyzes the diff against the base branch to surface SQL safety issues, LLM trust boundary violations, conditional side effects, and other structural risks before changes land.

Core Features & Use Cases

  • Diff analysis across PRs to surface safety, trust, and side-effect risks.
  • Proactive merge-readiness suggestions to prevent unsafe landings.
  • Use cases include code review, PR triage, and pre-landing checks on complex changes.

Quick Start

Run the review on a target PR to surface key risks before merging.

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 code review for pull requests?▼

Pre-landing code review is automated by analyzing the PR diff to surface SQL safety issues, LLM trust boundary violations, and conditional side effects before changes merge.

What specific risks should a pre-landing PR review check for?▼

A pre-landing PR review should check for SQL safety issues, LLM trust boundary violations, conditional side effects, and structural risks to prevent unsafe landings into the base branch.

How does diff analysis surface merge-readiness risks in feature branches?▼

Diff analysis compares feature branch changes against the base branch to proactively identify safety, trust, and side-effect risks, generating merge-readiness suggestions before unsafe landings occur.

Can I use automated code review for PR triage on complex changes?▼

Yes, automated code review supports PR triage on complex changes by evaluating the diff to surface structural risks and merge-readiness issues across code changes and feature branches.

What is the best way to prevent unsafe merges in a pull request workflow?▼

The best way to prevent unsafe merges is running pre-landing checks that analyze PR diffs for SQL safety, LLM trust boundaries, and conditional side effects before allowing changes to land.

How do I respond to findings from an automated PR diff review?▼

You respond to automated PR diff review findings by following the defined gstack review workflow, which outlines the exact checks performed, expected outcomes, and remediation steps for identified risks.

Related Skills

Explore More Software Engineering Skills→
timurgaleevtimurgaleev
5

review

Diagnose PR diffs for SQL safety and LLM trust boundary issues.

Community
Advanced
mattothomasmattothomas

review

Analyze PR diffs for SQL safety, LLM trust boundary violations, and side-effect risks.

Community
Intermediate
bordenetbordenet
8

progressive-code-review-gate

Automate progressive code review before commits and pushes.

Community
Advanced
ajsai47ajsai47
11

review

Analyze git diffs for SQL injection, race conditions, and shell injection risks.

Community
Advanced