review

Analyze diffs against the base branch to surface structural issues in PRs.

Updated Mar 13, 2026

Search Tags:#review #diff #code-quality #pull-request #sql-safety #llm-trust

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR review automation that analyzes diffs against the base branch to surface structural issues, including SQL safety and LLM trust boundary violations, so reviewers can act before merging.

Core Features & Use Cases

Diff comparison against base branch to identify risk areas like unsafe SQL, missing validations, and potential side effects.
Proactive suggestions for merge readiness and code quality improvements during PR prep.
Supports structured AskUserQuestion flows to gather input when ambiguous decisions are needed.

Quick Start

Run the review workflow on a PR to automatically inspect the diff against main and present findings and remediation paths.

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 reviews for unsafe SQL and side effects?▼

Automating pre-landing PR reviews involves analyzing diffs against the base branch to surface structural issues like unsafe SQL and conditional side effects. This process proactively suggests merge-readiness improvements before code is merged.

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

An LLM trust boundary violation occurs when unvalidated inputs cross security perimeters. Pre-landing diff analysis identifies these potential risks in your pull request, ensuring proper validations are enforced before merging.

How do I analyze code diffs against the main branch to prepare a pull request?▼

To analyze code diffs against the main branch, run a structured review workflow on your PR. This stages a checklist-driven inspection of the changes, identifies risk areas, and can auto-fix mechanical issues or prompt for input.

Can I automatically fix mechanical code quality issues during PR preparation?▼

Yes, you can automatically fix mechanical issues during PR preparation. The review workflow validates changes via a staged checklist, auto-fixing mechanical errors while prompting for user input when ambiguous judgment is required.

What's the best way to check merge readiness for structural code changes?▼

The best way to check merge readiness is comparing PR diffs against the base branch to detect missing validations and potential side effects. This proactive analysis surfaces structural issues so reviewers can act before merging.

How does a review workflow handle ambiguous decisions in diff analysis?▼

Diff analysis handles ambiguous decisions by using structured AskUserQuestion flows. When judgment is required rather than mechanical fixes, the review workflow pauses to gather user input, ensuring accurate remediation paths.