skills.rest
apeejay-education
apeejay-educationOFFICIAL
Explore all skills by this author →
GitHub

review

Analyze pull request diffs for SQL safety and LLM trust boundaries.

1|Updated Mar 26, 2026
Search Tags:#automation#code-review#pr-review#diff-analysis#sql-safety#llm-trust#pre-landing
One-click install
npx skills add https://github.com/apeejay-education/cadencesprout --skill review-apeejay-education
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/apeejay-education/cadencesprout/tree/main/.agents/skills/gstack-review
Command: npx skills add https://github.com/apeejay-education/cadencesprout --skill review-apeejay-education

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify structural and safety issues in diffs during pre-landing PR reviews by analyzing changes against the base branch.

Core Features & Use Cases

  • Analyze pull request diffs for SQL safety, LLM trust boundaries, and conditional side effects.
  • Proactively suggest fixes and guardrails before merging to improve code quality and safety.
  • Use case: when reviewing a PR that touches database queries or model prompts, surface risks and provide safe alternatives.

Quick Start

Review the current PR by analyzing the diff against the base branch for SQL safety, LLM trust boundaries, and conditional side effects, and proactively suggest fixes before merging.

Frequently Asked Questions about review

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

FAQPage Schema
How do I analyze pull request diffs for SQL safety before merging?▼

PR diff analysis identifies structural and safety issues in code changes against the base branch. It focuses on detecting SQL safety risks, LLM trust boundary violations, and conditional side effects before code merges.

What are LLM trust boundaries and how do I check them in code reviews?▼

LLM trust boundary checks identify unsafe model prompt modifications in pull requests. Analyzing diffs against the base branch surfaces potential trust risks and suggests safe alternatives before merging.

Can I detect conditional side effects in pull requests before landing code?▼

Yes, pre-landing PR review identifies conditional side effects by analyzing diffs against the base branch. It detects potential side effects across code changes and suggests proactive fixes to improve safety before merging.

What is the best way to automate pre-landing code reviews for risky diffs?▼

Automated pre-landing code review analyzes pull request diffs against the base branch to detect SQL safety, LLM trust boundary, and side effect risks. It proactively suggests fixes and guardrails to improve code safety before merging.

Does pre-landing PR review work without external dependencies?▼

Pre-landing PR review operates without external dependencies. It analyzes pull request diffs against the base branch to identify SQL safety, LLM trust boundary, and conditional side effect issues independently.

Related Skills

Explore More Software Engineering Skills→
jm199seojm199seo

review

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

Community
Advanced
Analog-LabsAnalog-Labs

review

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

Official
Advanced
idiaz01idiaz01
3

springboot-verification

Orchestrates build, static analysis, tests with Jacoco coverage, and security scans for Spring Boot projects in CI pipelines.

Community
Advanced
zzxtbetazzxtbeta

review

Analyze PR diffs against the base branch for SQL safety, prompt risks, and side effects.

Community
Advanced