review

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

Updated Jul 3, 2025
One-click install
npx skills add https://github.com/andrew-t-james/dotfiles --skill review-andrew-t-james
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/andrew-t-james/dotfiles/tree/main/dot_claude/skills/review
Command: npx skills add https://github.com/andrew-t-james/dotfiles --skill review-andrew-t-james

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the assessment of PR diffs for SQL safety, LLM trust, and potential side effects to prevent risky changes.

Core Features & Use Cases

  • PRE-landing PR reviews surface SQL safety checks, trust boundaries, and conditional side effects.
  • Use cases include reviewing code diffs before merging to catch unsafe SQL, data leakage, or unsafe prompts.

Quick Start

Run the pre-landing PR review to verify SQL safety, LLM trust boundaries, and conditional side effects on the diff.

Frequently Asked Questions about review

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

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

To check a PR diff for SQL safety, you can run an automated pre-landing review that analyzes the changes to identify unsafe SQL, enforce prompt-based decisions, and surface actionable guidance before merging.

How do I review code diffs to catch LLM trust boundary violations?

You can review code diffs to catch LLM trust boundary violations by applying an automated pre-landing assessment that inspects changes for data leakage, unsafe prompts, and trust violations across repositories.

What is a pre-landing PR review and when do I need it?

A pre-landing PR review is an automated assessment of code changes applied before merging to catch risky modifications. You need it when you want to prevent unsafe SQL, data leakage, and conditional side effects from landing in your repositories.

Can I use automated diff checks to detect conditional side effects in my code?

Yes, you can use automated diff checks to detect conditional side effects. The review process inspects PR diffs to verify safety constraints and surface potential side effects before the code merges.

What is the best way to automate code reviews for data leakage in LLM applications?

The best way to automate code reviews for data leakage in LLM applications is to run a pre-landing PR assessment that analyzes diffs for LLM trust boundaries, verifying safety constraints and surfacing actionable guidance.

Are there limitations to automated PR reviews for SQL safety and LLM trust?

Automated PR reviews for SQL safety and LLM trust focus on inspecting diffs to enforce prompt-based decisions. They require available tools to verify constraints and may not catch issues outside the analyzed diff context.