skills.rest
shaythegay13
shaythegay13COMMUNITY
Explore all skills by this author →
WebsiteGitHub

review

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

Updated Oct 25, 2025
Search Tags:#automation#review#code-quality#pull-request#diff-analysis#sql-safety#llm-boundaries
One-click install
npx skills add https://github.com/shaythegay13/serenity-pocket-app-final --skill review-shaythegay13
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/shaythegay13/serenity-pocket-app-final/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/shaythegay13/serenity-pocket-app-final --skill review-shaythegay13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly surface structural issues in a PR by analyzing the diff against the base branch to identify SQL safety risks, LLM trust boundary violations, and unintended side effects. This helps teams review code changes with confidence and merge safer, higher-quality updates.

Core Features & Use Cases

  • Diff analysis for SQL safety and potential injection risks.
  • LLM trust boundary checks to prevent leakage or unsafe prompts.
  • Detection of conditional side effects and hidden dependencies.
  • Pre-landing guidance and actionable recommendations to harden changes.
  • Proactive merge-readiness suggestions to avoid risky landings.

Quick Start

To start a review, provide the PR diff and base context and run the skill to receive a structured, actionable report.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate code review for pull requests before merging?▼

Pre-landing pull request reviews analyze diffs against the base branch to detect SQL injection risks, LLM trust boundary violations, and conditional side effects, returning a structured report with recommended fixes and rationale to guide safer merges.

What is diff analysis for SQL safety and how does it work?▼

SQL safety diff analysis compares PR changes against the base branch to identify potential injection risks, surfacing structural issues in modified code to help teams review changes and merge safer, higher-quality updates confidently.

How do I check LLM trust boundaries in my code changes?▼

Check LLM trust boundaries by running a pre-landing review that analyzes PR diffs for potential leakage or unsafe prompts, identifying boundary violations to prevent unintended data exposure or unsafe LLM interactions before code lands.

Can I detect conditional side effects and hidden dependencies in a PR diff?▼

Detect conditional side effects and hidden dependencies by analyzing a PR diff against the base branch, surfacing these structural issues to help teams review code changes with confidence and avoid risky landings.

What do I need to provide to start a pre-landing code review?▼

Start a pre-landing code review by providing the PR diff and base context; running the skill on these inputs produces a structured, actionable report with recommended fixes and rationale to guide the reviewer through changes.

What is the best way to get merge-readiness suggestions for risky code changes?▼

Get merge-readiness suggestions by running an automated pre-landing review on the PR diff, which proactively suggests improvements and actionable recommendations to harden changes, helping avoid risky landings and merge safer updates.

Related Skills

Explore More Software Engineering Skills→
Kevin-Liu-01Kevin-Liu-01
16

pr

Create pull requests with the Dedalus template and git state.

Community
Intermediate
heliohqheliohq
88

handoff

Coordinates GitHub pull requests from commit to ready-for-merge state.

Official
Advanced
tblakex01tblakex01
1

review

Analyze pull request diffs for SQL safety and trust boundary issues.

Community
Advanced
ajsai47ajsai47
11

review

Analyze git diffs for SQL injection, race conditions, and shell injection risks.

Community
Advanced