review

Analyze PR diffs for SQL safety, LLM trust boundaries, and structural risks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated pre-landing PR reviews analyze diffs against the base branch to detect SQL safety violations, LLM trust boundary issues, and potential side effects before merging.

Core Features & Use Cases

  • Diff analysis for SQL safety and data integrity checks
  • LLM trust boundary enforcement and prompt leakage detection
  • Scope and impact assessment with actionable remediation notes
  • Proactive flagging of merge risks and policy violations
  • Works on PR reviews, code reviews, or direct diff checks

Quick Start

Say: "Review this PR against the base branch and report any SQL, LLM, or structural issues."

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate a pre-landing PR review for SQL safety and structural risks?

Automated pre-landing PR review analyzes your git diffs against the base branch to detect SQL safety violations, LLM trust boundary issues, and conditional side effects before merging.

What does an automated code review check for in LLM trust boundaries?

Automated code review checks LLM trust boundaries by analyzing diffs to detect prompt leakage risks, enforce trust limits, and identify potential side effects before merging changes.

Can I use this to review my diff directly instead of a full pull request?

Yes, you can review your diff directly by asking it to check your diff, which triggers the same structural risk analysis and merge policy violation flagging as a full PR review.

What is the best way to unblock merging after a pre-landing code review?

The best way to unblock merging is to apply the actionable remediation notes provided by the review, which highlight specific issues and suggest changes to resolve merge risks.

Does automated PR review work without configuring additional dependencies?

Yes, automated PR review works without additional dependencies, directly analyzing your base branch diffs to assess scope and impact while flagging structural risks.