review

Analyze diffs against the base branch to detect structural issues and policy violations in PRs.

2|Updated Mar 31, 2026

Search Tags:#LLM #merge #review #diff #PR #gstack

Ready to run

npx skills add https://github.com/jayzalowitz/skytwin --skill review-jayzalowitz

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes diffs against the base branch to surface structural issues, LLM trust boundary concerns, conditional side effects, and other defects in PRs. It helps teams catch issues before merging and keeps code safe and maintainable.

Core Features & Use Cases

Detects SQL safety concerns, risky shell usage, and side-effect risks in diffs.
Flags LLM trust boundary violations and policy routing concerns in PR changes.
Proactively suggests optimizations, gating steps, or routing adjustments before land.

Quick Start

Run /review on your branch to start the pre-landing PR review against the base branch.

Frequently Asked Questions about review

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

FAQPage Schema

How do I run a pre-landing PR review on my current branch?▼

Run /review on your branch to start a pre-landing PR review against the base branch. It analyzes your diff to surface structural issues and policy violations before merging.

What does a pre-landing PR review check for in a diff?▼

A pre-landing PR review checks diffs for SQL safety concerns, risky shell usage, side-effect risks, and LLM trust boundary violations. It also proactively suggests optimizations and gating steps before land.

Can I use this PR review tool with both GitHub and GitLab merge checks?▼

Yes, this PR review tool is designed for pre-landing reviews and merge checks across both GitHub and GitLab. It loads repository context to surface actionable feedback on code changes.

How do I detect LLM trust boundary violations in a pull request?▼

To detect LLM trust boundary violations in a pull request, run a diff analysis against your base branch. The review flags policy routing concerns and LLM trust boundary issues in PR changes.

What is the best way to catch risky shell usage and SQL safety issues before merging?▼

The best way to catch risky shell usage and SQL safety issues before merging is to run an automated diff analysis. It surfaces these structural defects and side-effect risks proactively during pre-landing review.