skills.rest
drt0927
drt0927COMMUNITY
Explore all skills by this author →
GitHub

review

Analyze PR diffs against the base branch for SQL safety and trust boundary issues.

5|1|Updated Feb 12, 2026
Search Tags:#review#code-quality#pull-request#diff-analysis#sql-safety#llm-trust#pre-landing
One-click install
npx skills add https://github.com/drt0927/tw-overlay --skill review-drt0927
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/drt0927/tw-overlay/tree/main/.gemini/skills/gstack-review
Command: npx skills add https://github.com/drt0927/tw-overlay --skill review-drt0927

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR diffs can hide SQL safety risks, unsafe LLM prompts, and side effects that slip into releases. This skill analyzes diffs against the base branch to surface structural issues before landing code.

Core Features & Use Cases

  • Diff-based SQL safety analysis and trust-boundary checks
  • Proactive risk signaling with concrete remediation guidance
  • Use Case: pre-landing PR reviews, code reviews, or diff checks to catch issues early

Quick Start

Run a diff review on the current branch against the base to surface SQL safety issues, trust boundary violations, and conditional side effects before 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 PR diff for SQL safety issues before merging?▼

A pre-landing code review analyzes a PR diff against the base branch to proactively surface SQL safety issues, LLM trust boundary violations, and conditional side effects to reduce merge risk before landing code.

How does diff analysis detect LLM trust boundary violations in a pull request?▼

Diff analysis detects LLM trust boundary violations by evaluating PR changes against the base branch to identify unsafe LLM prompts and structural risks, guiding reviewers with concrete guardrails before merging.

What is the best way to perform a pre-landing review on a risky pull request?▼

The best way to perform a pre-landing review is to analyze the PR diff against the base branch, which proactively surfaces conditional side effects and trust boundary violations with actionable recommendations to reduce merge risk.

Can I use automated diff analysis to catch conditional side effects in my code review?▼

Yes, you can use automated diff analysis during a code review to catch conditional side effects by evaluating the PR diff against the base branch and signaling risks with concrete remediation guidance.

When do I need a pre-landing code review for SQL safety and LLM trust boundaries?▼

You need a pre-landing code review when your PR diff introduces database queries or LLM prompts, analyzing the changes against the base branch to surface SQL safety issues and trust boundary violations before merging.

Related Skills

Explore More Software Engineering Skills→
SeaLion-hubSeaLion-hub

review

Analyze pull request diffs for SQL safety, trust boundaries, and side effects.

Community
Advanced
mdmagnuson-creatormdmagnuson-creator

merge-conflicts

Merge target branches into source branches and resolve pull request conflicts.

Community
Advanced
rkumar261rkumar261
1

review

Analyze PR diffs for SQL safety, trust boundary, and side-effect issues.

Community
Advanced
devopstalesdevopstales
1

semgrep-security

Scan source code for security vulnerabilities and code quality issues with Semgrep.

Community
Intermediate