skills.rest
AndrewLi0420
AndrewLi0420COMMUNITY
Explore all skills by this author →
GitHub

review

Analyze pull request diffs for SQL safety and trust boundary issues.

Updated Mar 18, 2026
Search Tags:#review#diff#code-review#pull-request#pr-review#sql-safety#llm-trust
One-click install
npx skills add https://github.com/AndrewLi0420/BMW --skill review-andrewli0420
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/AndrewLi0420/BMW/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/AndrewLi0420/BMW --skill review-andrewli0420

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR review identifies diffs against the base branch to catch SQL safety issues, LLM trust boundary violations, conditional side effects, and other structural concerns.

Core Features & Use Cases

  • Comprehensive diff analysis for SQL safety, data integrity, and risk assessment before merges.
  • Guidance on LLM trust boundaries, prompt hygiene, and risk-aware changes.
  • Use case: a developer asks to pre-review a PR to ensure no unintended changes reach production.

Quick Start

Run the /review workflow on a PR to automatically scan the diff for SQL safety, LLM trust boundaries, and structural issues.

Frequently Asked Questions about review

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

FAQPage Schema
How do I perform a pre-landing PR review for SQL safety and LLM trust boundaries?▼

Pre-landing PR review analyzes pull request diffs against the base branch to detect SQL safety issues, LLM trust boundary violations, and conditional side effects. Running a dedicated review workflow scans the diff to ensure safe and reliable merges before code reaches production.

What structural concerns can a code review workflow find in a diff?▼

A code review workflow evaluates pull request diffs to find SQL safety issues, data integrity risks, LLM trust boundary violations, conditional side effects, and structural concerns. It applies a two-pass workflow providing actionable outcomes that guide quality, safety, and maintainability improvements before landing.

How do I check pull request diffs for unintended changes before merging?▼

Checking pull request diffs for unintended changes involves analyzing code against the base branch to catch conditional side effects and structural concerns. A pre-landing review workflow automatically scans these diffs to prevent unintended changes from reaching production environments.

Does pre-landing diff analysis require external dependencies to scan for SQL safety?▼

Pre-landing diff analysis requires no external dependencies to scan for SQL safety and LLM trust boundaries. The review workflow operates self-contained to analyze pull request diffs and provide actionable outcomes for safe merges.

What is the best way to review a diff for LLM trust boundary violations?▼

The best way to review a diff for LLM trust boundary violations is applying a two-pass workflow that analyzes changes against the base branch. This approach evaluates prompt hygiene, risk-aware changes, and trust boundaries to guide maintainability improvements before landing the pull request.

Related Skills

Explore More Software Engineering Skills→
AkbarDevopAkbarDevop

review

Identify production-risk findings in a code diff before merging.

Community
Advanced
shaythegay13shaythegay13

review

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

Community
Advanced
yanochka11yanochka11

review

Analyze repository diffs to identify defects, security risks, and structural problems.

Community
Advanced
Codagent-AICodagent-AI
30

fix-pr

Resolve CI failures and review comments on GitHub pull requests.

Official
Advanced