skills.rest
ekrishgupta
ekrishguptaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

review

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

1|3|Updated Mar 19, 2026
Search Tags:#review#diff#code-quality#pull-request#sql-safety#llm-trust#pre-landing
One-click install
npx skills add https://github.com/ekrishgupta/gemstack --skill review-ekrishgupta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/ekrishgupta/gemstack/tree/main/review
Command: npx skills add https://github.com/ekrishgupta/gemstack --skill review-ekrishgupta

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". Proactively suggest when the user is about to merge or land code changes.

Core Features & Use Cases

  • Analyzes diffs for SQL safety, LLM trust boundary violations, and conditional side effects.
  • Proactively surfaces actionable issues and recommended next steps before merging.
  • Use cases: when reviewing a PR, checking a diff, or ensuring code changes won't regress safety or trust requirements.

Quick Start

Run the /review workflow on your branch to surface critical issues against the base diff and guide safe merging.

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 landing a pull request?▼

To check your diff for SQL safety before landing a pull request, run a pre-landing review against the base branch. This analyzes the changes to surface unsafe SQL patterns and provides guidance on safe merge decisions.

What is pre-landing code review and how does it detect LLM trust boundary violations?▼

Pre-landing code review analyzes branch diffs against the base to identify LLM trust boundary violations and conditional side effects. It proactively flags these critical structural issues before merging to prevent safety regressions.

How do I perform an automated code review on a PR diff?▼

Perform an automated code review by running the review workflow on your branch. It compares the diff against the base branch to identify critical issues affecting code quality, SQL safety, and trust boundaries, then records artifacts for auditing.

Does this pre-landing review work without any external dependencies?▼

Yes, the pre-landing review works without external dependencies. It requires clear criteria for detecting unsafe patterns within your diff to successfully surface actionable issues and record artifacts for auditing.

When should I use an automated diff check instead of manual code review?▼

Use an automated diff check when you are about to merge or land code changes affecting SQL safety or LLM trust boundaries. It proactively surfaces structural issues and conditional side effects that manual reviews might miss.

Related Skills

Explore More Software Engineering Skills→
kage1020kage1020

diff-report

Analyze branch changes and generate a five-section Markdown diff report.

Community
Intermediate
MoonLadderStudiosMoonLadderStudios
12

pr-resolver

Orchestrate GitHub pull request resolution with bounded retries and structured artifacts.

Official
Advanced
MomoDavilukeMomoDaviluke
2

verification-loop

Automate builds, type checks, linting, tests, and security scans for Claude Code sessions.

Community
Advanced
Srujan0798Srujan0798

security-auditor

Detect OWASP Top 10 vulnerabilities in code changes with structured alerts.

Community
Intermediate