review

Analyze diffs against the base branch for SQL safety and structural issues.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Chang-Shih-Yung/auto-learning --skill review-chang-shih-yung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Chang-Shih-Yung/auto-learning/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/Chang-Shih-Yung/auto-learning --skill review-chang-shih-yung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when asked to "review this PR", "code review", "pre-landing review", or "check my diff".

Core Features & Use Cases

  • Analyzes diffs against the base branch to detect SQL safety issues, LLM trust boundary violations, conditional side effects, and structural problems.
  • Proactively suggests actions when the user is about to merge or land code changes.
  • Supports workflows when asked to review a PR, code review, pre-landing review, or check a diff.

Quick Start

Ask Claude to review the current diff by running /review on the PR.

Frequently Asked Questions about review

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

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

Pre-landing code review analyzes your diff against the base branch to detect SQL safety issues, LLM trust boundary violations, and conditional side effects. It inspects structural problems and guides fixes before code lands.

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

Pre-landing PR review identifies structural problems and security risks in your code changes before they are merged. You need it when you want to check a diff for SQL safety, LLM trust boundaries, or conditional side effects.

How do I run a code review on my current pull request?

You can run a code review by asking Claude to review your current diff. Use commands like 'review this PR' or 'check my diff' to trigger analysis against the base branch and surface findings.

Does pre-landing review detect LLM trust boundary violations?

Yes, pre-landing review specifically detects LLM trust boundary violations. It analyzes your diff to ensure trust boundaries are maintained and proactively suggests actions when a merge is imminent.

Can I use this to review conditional side effects in my code changes?

Yes, pre-landing PR review analyzes diffs against the base branch to identify conditional side effects. It inspects your code changes to surface structural problems and guide necessary fixes.

What's the best way to proactively review code before a merge?

Pre-landing review proactively suggests actions when a merge is imminent by analyzing your diff against the base branch. It identifies SQL safety issues, LLM trust boundary violations, and structural problems to guide fixes.