review

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

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/pistosmin/base-one --skill review-pistosmin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/pistosmin/base-one/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/pistosmin/base-one --skill review-pistosmin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze the current PR diff against the base branch to surface structural issues not caught by tests, including SQL safety, LLM trust boundaries, and conditional side effects, enabling safer merge decisions.

Core Features & Use Cases

  • Two-pass review workflow that first checks critical risks (SQL safety, LLM trust boundaries) and then surfaces informational findings.
  • Scope Drift Detection: compare intent vs. implementation to ensure the PR aligns with requested work.
  • Proactive guidance: generates actionable remediation steps, including tests, documentation, and code changes.

Quick Start

Run the /review workflow on your current branch to analyze the diff against the base branch and generate a review report.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a PR diff for structural issues not caught by tests?

Pre-landing PR review analyzes the current branch against the base branch to surface structural issues not caught by tests, including SQL safety, LLM trust boundaries, and conditional side effects. It runs a two-pass workflow checking critical risks first, then informational findings.

What is scope drift detection in code review?

Scope drift detection compares PR intent versus implementation to ensure the diff aligns with requested work. It surfaces deviations from the original scope during pre-landing review, helping reviewers and authors identify unintended changes before merge decisions.

How do I check SQL safety in a pull request before merging?

PR review analyzes the branch diff against the base branch to check SQL safety as a critical risk in its first pass. It examines SQL changes within the diff to identify potential safety issues and generates actionable remediation steps including tests and code changes.

Can I use automated PR review to validate LLM trust boundaries?

PR review includes LLM trust boundary checks as a critical risk in its first pass, analyzing the diff for GPT prompt integrity and trust boundary issues. It surfaces these findings before informational checks to enable safer merge decisions.

What's the best way to generate remediation guidance for pull request reviewers?

PR review generates actionable remediation steps including tests, documentation, and code changes after analyzing the branch diff. It produces a structured plan for reviewers and authors by integrating checks for SQL safety, GPT prompt integrity, checklists, and optional triage steps.

Does pre-landing PR review work without external dependencies?

PR review operates with no external dependencies, analyzing the current branch diff against the base branch directly. It runs its two-pass workflow covering SQL safety, LLM trust boundaries, and conditional side effects without requiring additional tools or integrations.