skills.rest
tblakex01
tblakex01COMMUNITY
Explore all skills by this author →
GitHub

review

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

1|Updated Apr 26, 2026
Search Tags:#LLM#review#pull-request#diff-analysis#sql-safety#pre-landing#trust-boundary
One-click install
npx skills add https://github.com/tblakex01/conductor-playground --skill review-tblakex01
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/tblakex01/conductor-playground/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/tblakex01/conductor-playground --skill review-tblakex01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR diffs can hide risky changes. This skill analyzes diffs against the base branch to surface SQL safety issues, LLM trust boundary violations, conditional side effects, and other structural concerns. It helps when someone says "review this PR", "code review", "pre-landing review", or "check my diff" by proactively suggesting actions before merge.

Core Features & Use Cases

  • Diff analysis against the base branch to identify risky patterns (SQL safety, trust boundaries, conditional side effects)
  • Proactive guidance to the user when changes look unsafe, including merge-landing suggestions
  • Handles multiple triggers and integrates with plan-mode safety constraints

Quick Start

Ask Claude to run a review on the current PR to get an automated safety assessment.

Frequently Asked Questions about review

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

FAQPage Schema
How do I check a pull request diff for SQL safety issues before merging?▼

To check a pull request diff for SQL safety issues before merging, you can run an automated pre-landing review. This analyzes the diff against the base branch to proactively surface SQL safety risks and structural concerns before code lands.

What is a pre-landing code review and how does it handle LLM trust boundaries?▼

A pre-landing code review analyzes pull request diffs to identify LLM trust boundary violations before merging. It proactively flags risky patterns and suggests actions to guide safe merge decisions when changes look unsafe.

Can I automate diff analysis to flag conditional side effects in my code?▼

Yes, you can automate diff analysis to flag conditional side effects in your code. By analyzing pull request diffs against the base branch, the review identifies structural concerns and risky patterns proactively before merge.

Does automated PR review work without additional dependencies?▼

Automated PR review works without additional dependencies. It analyzes diffs to surface SQL safety issues, LLM trust boundary violations, and conditional side effects by integrating with allowed tools to trigger alerts.

What is the best way to review PR diffs for risky patterns before landing code?▼

The best way to review PR diffs for risky patterns before landing code is running an automated pre-landing review. It analyzes the diff against the base branch to surface SQL safety issues, LLM trust boundary violations, and structural concerns.

Related Skills

Explore More Software Engineering Skills→
anilveersingh1308anilveersingh1308

review-pr

Review pull request diffs against a base branch for risk and impact.

Community
Intermediate
concept2cureconcept2cure

review

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

Community
Advanced
fredrick84823fredrick84823
2

deep-module

Draft and evaluate modular designs to enforce clean module boundaries.

Community
Intermediate
steadyfallsteadyfall

review

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

Community
Advanced