skills.rest
lemig
lemigCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

review

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

Updated May 14, 2026
Search Tags:#security#code-review#pr-review#diff-analysis#gstack#llm-trust#pre-landing
One-click install
npx skills add https://github.com/lemig/transcriptor --skill review-lemig
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/lemig/transcriptor/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/lemig/transcriptor --skill review-lemig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes diffs against the base branch to surface risks in PRs, including SQL safety, LLM trust boundary violations, and conditional side effects, enabling safer pre-landing reviews.

Core Features & Use Cases

  • Diff analysis for SQL safety, data exposure, and security patterns in pull requests.
  • LLM trust-boundary checks to prevent prompt injection and data leakage within diffs.
  • Proactive merge guidance: suggests fixes, routing decisions, and quality gates before merging.

Quick Start

Provide the PR diff to review and I will perform a pre-landing analysis for SQL safety, LLM trust boundaries, and structural risks.

Frequently Asked Questions about review

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

FAQPage Schema
How do I analyze a PR diff for SQL safety and security risks before merging?▼

PR diff analysis for SQL safety and security risks evaluates code changes against the base branch to surface data exposure and structural threats. This pre-landing review identifies potential issues before merging.

What is an LLM trust boundary violation in code review?▼

An LLM trust boundary violation occurs when code changes risk prompt injection or data leakage within the model's execution context. Diff analysis checks code to prevent these security vulnerabilities.

How do I check pull request diffs for conditional side effects?▼

Checking pull request diffs for conditional side effects involves analyzing code changes to identify hidden structural risks and unintended operations. This pre-landing analysis provides actionable recommendations before merging.

Can I get actionable merge guidance and risk scores from a diff analysis?▼

Yes, a pre-landing diff analysis can generate risk scores across SQL safety, LLM trust boundaries, and side effects. It provides actionable recommendations, suggested fixes, and routing decisions for safe merges.

What is the best way to prevent prompt injection vulnerabilities in a pull request?▼

Preventing prompt injection vulnerabilities in a pull request requires analyzing diffs for LLM trust boundary violations before merging. This review clarifies risk scores and suggests fixes to prevent data leakage.

When do I need a pre-landing code review?▼

You need a pre-landing code review when you want to surface design and security issues before merging code. Analyzing PR diffs against the base branch ensures safe, trusted merges by identifying SQL safety and side effect risks.

Related Skills

Explore More Software Engineering Skills→
jm199seojm199seo

review

Analyze pull request diffs against the base branch for structural issues.

Community
Advanced
TacuchiTacuchi

git

Verify the work branch and require approval before executing Git commits.

Community
Advanced
CarbeneAICarbeneAI
9

review

Identifies defects and risks in a PR diff by analyzing SQL safety, LLM trust boundaries, and side effects.

Community
Advanced
temple-slopetemple-slope

security

Review git diffs for secrets, vulnerabilities, and injections.

Community
Intermediate