review

Analyze diffs for SQL safety, LLM trust boundaries, and conditional side effects.

37|2|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/DariusCorvus/iqualize --skill review-dariuscorvus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/DariusCorvus/iqualize/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/DariusCorvus/iqualize --skill review-dariuscorvus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR reviews often miss subtle structural issues in diffs that can slip into production. This Skill analyzes the diff against the base branch to surface SQL safety problems, LLM trust boundary violations, conditional side effects, and other structural issues before merge.

Core Features & Use Cases

  • Analyzes diffs for SQL safety, LLM trust boundaries, and side effects.
  • Proactively suggests merge/safe landing actions during pre-landing reviews.
  • Use cases: when asked to "review this PR", "code review", "pre-landing review", or "check my diff", surface issues early and guide next steps.

Quick Start

Pass the current PR diff to the review skill to surface SQL safety issues, LLM trust boundaries, and plan safe merge steps.

Frequently Asked Questions about review

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

FAQPage Schema
How do I check my diff for SQL safety issues before merging?

To check your diff for SQL safety issues, you can run an automated pre-landing PR review against the base branch to surface injection risks and unsafe query structures before merge.

What is an LLM trust boundary violation in a code review?

An LLM trust boundary violation occurs when untrusted model outputs access privileged actions without validation; automated code review identifies these structural risks within the current diff.

How do I automate a pre-landing review to detect conditional side effects?

Automating a pre-landing review analyzes your PR diff against the base branch to detect conditional side effects, generating proactive merge-safety prompts and actionable recommendations.

Can I use automated code review for structural issues without configuring dependencies?

Automated code review for structural issues operates without external dependencies, analyzing the current diff directly to identify SQL safety and LLM trust boundary violations.

What is the best way to surface merge-safety problems in a PR?

The best way to surface merge-safety problems is analyzing the diff against the base branch to proactively identify SQL safety, LLM trust boundaries, and conditional side effects before landing.