skills.rest
rshelekhov
rshelekhovCOMMUNITY
Explore all skills by this author →
GitHub

review

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

Updated Nov 11, 2025
Search Tags:#code-quality#pr-review#diff-analysis#gatekeeper#sql-safety#llm-trust
One-click install
npx skills add https://github.com/rshelekhov/dotfiles --skill review-rshelekhov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/rshelekhov/dotfiles/tree/main/claude/skills/gstack/review
Command: npx skills add https://github.com/rshelekhov/dotfiles --skill review-rshelekhov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR review helps teams catch structural and safety issues before merging by analyzing the diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other risk indicators.

Core Features & Use Cases

  • Analyze diffs for SQL safety and data integrity issues.
  • Detect LLM trust boundary violations and potential side effects.
  • Identify conditional side effects and structural inconsistencies.
  • Provide actionable recommendations and checklists to guide reviewers.
  • Integrate with PR workflows to speed up governance reviews.

Quick Start

Run the pre-landing PR review on your current branch to receive a structured diff analysis and actionable findings.

Frequently Asked Questions about review

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

FAQPage Schema
How do I run a pre-landing PR review for SQL safety issues?▼

Pre-landing PR review analyzes your branch diff against the base branch to detect SQL safety issues and conditional side effects. You run the review on your current branch to receive a structured diff analysis and actionable findings.

What is an LLM trust boundary violation in a pull request diff?▼

An LLM trust boundary violation occurs when a diff introduces code that improperly handles LLM inputs or outputs, compromising safety. The review identifies these potential side effects alongside structural inconsistencies before merging.

How does diff analysis detect conditional side effects before merging?▼

Diff analysis detects conditional side effects by comparing the pull request changes against the base branch to identify structural problems and risk indicators. This process provides a structured checklist to guide reviewers.

Can I use automated PR review for governance and merge safety checks?▼

Yes, automated PR review integrates with governance workflows to speed up merge safety checks. It analyzes diffs for SQL safety, LLM trust boundaries, and structural problems to ensure safe code integration.

What's the best way to identify structural problems in a code diff?▼

The best way to identify structural problems in a code diff is using an automated pre-landing review that applies a structured checklist and stepwise workflow to detect inconsistencies and safety issues before merge.

Do I need dependencies to run a pre-landing code review?▼

No dependencies are required to run this pre-landing code review. The skill operates independently to analyze your pull request diff and provide actionable recommendations for reviewers.

Related Skills

Explore More Software Engineering Skills→
westnwestn
1

review

Identify structural issues in diffs and PR context before merging.

Community
Advanced
u1pnsu1pns
8

code-reviewer

Identify security, quality, and performance risks in codebases before merge.

Community
Advanced
Obsidian-OwlObsidian-Owl
9

gate-wiring

Detect unused exports, orphaned files, layer violations, and circular dependencies in changed code.

Official
Intermediate
DaBigHomieDaBigHomie
1

malfig

Automate pre-commit gatekeeper checks for IDE integrity and import-layer policy on management-git repos.

Community
Advanced