review

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

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/singhianand23045/GarryTan --skill review-singhianand23045
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/singhianand23045/GarryTan/tree/main/review
Command: npx skills add https://github.com/singhianand23045/GarryTan --skill review-singhianand23045

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR review analyzes the diff against the base branch to surface SQL safety issues, LLM trust boundary violations, conditional side effects, and other structural risks before merging. It helps teams enforce quality gates and catch issues early in the PR workflow.

Core Features & Use Cases

  • Analyze diffs for SQL safety, LLM trust boundaries, conditional side effects, and other structural issues.
  • Proactively suggest when a user is about to merge or land code changes.
  • Provide actionable findings with prioritized recommendations and clear next steps for engineers.

Quick Start

Describe the PR you want reviewed (for example, "review this PR") and the skill will analyze the diff against the base branch for safety and structure.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review code diffs for SQL safety and LLM trust boundary violations before merging?

Pre-landing PR review analyzes your code diffs against the base branch to identify SQL safety issues, LLM trust boundary violations, and conditional side effects before merging. It returns actionable findings with prioritization and recommended fixes.

What is pre-landing code review and how does it enforce quality gates?

Pre-landing code review is the process of analyzing a diff against the base branch to surface structural risks before merging. It enforces quality gates by catching SQL safety, LLM trust, and conditional side effect issues early in the PR workflow.

How do I check my pull request for conditional side effects and structural risks?

To check your pull request for conditional side effects, describe the PR you want reviewed. The skill analyzes the diff against the base branch for structural risks, providing actionable findings with clear next steps and a concise completion summary.

Can I use automated diff checks to catch LLM trust boundary issues in my base branch?

Yes, automated diff checks can catch LLM trust boundary issues by analyzing your code changes against the base branch. The review process proactively surfaces these violations alongside SQL safety and conditional side effect concerns before landing.

What are the limitations of automated pre-landing PR review for code quality?

Automated pre-landing PR review focuses specifically on SQL safety, LLM trust boundaries, and conditional side effects in diffs. It does not replace human review but provides prioritized, actionable findings to help engineers catch structural risks early.

Does pre-landing PR review work with existing code review workflows?

Pre-landing PR review integrates with existing code review workflows by analyzing diffs against the base branch. You simply describe the PR you want reviewed, and it returns prioritized findings and recommended fixes to support your current process.