review

Analyze PR diffs for SQL safety, LLM trust boundaries, and structural issues.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/diiviikk5/rezops --skill review-diiviikk5
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/diiviikk5/rezops/tree/main/review
Command: npx skills add https://github.com/diiviikk5/rezops --skill review-diiviikk5

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR reviews require thorough checks of code diffs against the base branch to catch SQL safety issues, LLM trust boundary violations, and potentially harmful conditional side effects. This Skill automates those checks and guides proactive quality gates before merges.

Core Features & Use Cases

  • Analyze PR diffs for SQL safety, LLM trust boundaries, and conditional side effects.
  • Surface issues early and suggest when a different rezops skill should be invoked.
  • Support use during "review this PR", "code review", "pre-landing review", or "check my diff" scenarios.

Quick Start

Review a PR diff to automatically analyze SQL safety and LLM trust boundaries.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate PR diff analysis for SQL safety issues?

Automating PR diff analysis checks code changes against the base branch to detect SQL safety violations, LLM trust boundary issues, and conditional side effects before merging. It surfaces proactive quality gates and actionable recommendations during pre-landing review.

What is an LLM trust boundary and how do I check it in a code review?

An LLM trust boundary defines where automated logic interacts safely with language model outputs. Checking it during code review involves analyzing PR diffs to identify violations and potentially harmful conditional side effects before landing changes.

Can I use automated diff analysis to catch structural issues before merging?

Yes, automated diff analysis evaluates PR diffs for structural issues, SQL safety, and LLM trust boundaries. It functions as a pre-landing quality gate to surface problems and suggest actionable recommendations before code merges.

What is the best way to run a pre-landing review for conditional side effects?

The best way to run a pre-landing review for conditional side effects is analyzing PR diffs automatically to detect harmful logic branches and LLM trust boundary violations. This surfaces proactive quality gates and actionable recommendations before merging.

Does automated PR review work without external dependencies?

Automated PR review operates without external dependencies, analyzing code diffs directly for SQL safety and structural issues. It functions independently to surface quality gates and suggest when different rezops skills should be invoked.

When should I not rely on automated diff analysis for code review?

Automated diff analysis focuses specifically on SQL safety, LLM trust boundaries, and structural issues. It should not replace human review for complex business logic, but rather surface proactive quality gates and suggest invoking other rezops skills when needed.