review

Analyze PR diffs against the base branch for SQL safety and trust boundary issues.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/XinheLIU/human-leverage --skill review-xinheliu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/XinheLIU/human-leverage/tree/main/.claude/skills/review
Command: npx skills add https://github.com/XinheLIU/human-leverage --skill review-xinheliu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes diffs against the base branch to surface structural issues during pre-landing PR reviews. It focuses on SQL safety, LLM trust boundaries, conditional side effects, and other risk signals that commonly slip through manual checks.

Core Features & Use Cases

  • Automated two-pass PR review guided by a CRITICAL-first checklist (SQL safety, trust boundaries) followed by INFORMATIONAL checks.
  • Surface actionable findings with file references, context, and recommended fixes, or prompt for input on items requiring human judgment.
  • Proactively highlight when a change is near merge time and suggest next steps to keep changes safe.

Quick Start

Run the /review workflow on the current branch to begin a pre-landing PR review against the base branch.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate pull request reviews for SQL safety and LLM trust boundaries?

Automated PR review analyzes branch diffs to surface SQL safety issues and LLM trust boundary violations. It uses a two-pass checklist approach to identify structural risks and ensure compliance before changes land.

What is a two-pass checklist approach for pre-landing code reviews?

A two-pass checklist approach runs CRITICAL checks first for SQL safety and trust boundaries, followed by INFORMATIONAL checks. This structured feedback surfaces actionable findings with file references and recommended fixes.

How do I analyze a PR diff against the base branch to surface conditional side effects?

Analyzing the current PR diff against the base branch detects conditional side effects and other structural concerns. It proactively highlights risk signals that commonly slip through manual code checks.

Can I get automated fix proposals for structural issues found during diff analysis?

Yes, diff analysis can propose fixes for detected structural issues. For items requiring human judgment, the review workflow will prompt for input to ensure safe changes near merge time.

Does this automated PR review workflow require any specific dependencies or components?

No specific dependencies or components are required to run the automated PR review workflow. You simply run the review process on the current branch to begin the pre-landing analysis against the base branch.

What are the limitations of using automated diff analysis for pull request reviews?

Automated diff analysis focuses on structural concerns like SQL safety and LLM trust boundaries, but cannot fully replace human judgment. It prompts for input on complex items rather than auto-resolving all review ambiguities.