skills.rest
timurgaleev
timurgaleevCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

review

Diagnose PR diffs for SQL safety and LLM trust boundary issues.

5|Updated Apr 24, 2026
Search Tags:#git#llm#sql#review#trust#diff#pull-request
One-click install
npx skills add https://github.com/timurgaleev/vibestack --skill review-timurgaleev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/timurgaleev/vibestack/tree/main/skills/review
Command: npx skills add https://github.com/timurgaleev/vibestack --skill review-timurgaleev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates a pre-landing pull request review by analyzing the diff against the base branch to identify SQL safety issues, LLM trust boundary violations, and unexpected side effects that could impact production.

Core Features & Use Cases

  • Analyzes diffs for SQL safety vulnerabilities and LLM trust boundary violations.
  • Checks for conditional side effects and structural issues that could affect merge readiness.
  • Provides actionable findings for pre-landing reviews, enabling teams to fix issues before shipping.

Quick Start

Trigger the review by running the /review command on a PR diff to surface actionable findings 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 a pull request diff for SQL safety issues before merging?▼

A pre-landing pull request review analyzes your diff against the base branch to surface SQL safety issues, LLM trust boundary violations, and structural risks before merging.

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

An LLM trust boundary violation occurs when untrusted data improperly crosses into model processing paths. A pre-landing diff review detects these structural risks and unexpected side effects before merge.

Can I run a pre-landing review on a git diff using bash and awk?▼

Yes, the pre-landing review requires shell utilities including bash, grep, and awk to parse git diff output, detect the base branch, and surface actionable validation findings before merge.

How do I automate governance checks for structural risks in a PR?▼

You automate governance checks by running a pre-landing review that diagnoses the diff against the base branch to identify conditional side effects, structural risks, and merge readiness issues before shipping.

What are the limitations of using diff analysis for pre-landing pull request reviews?▼

Limitations include the strict requirement for git diff output, a detected base branch, and specific shell utilities like bash and awk. The review cannot function without these inputs or outside its targeted scope of SQL and LLM checks.

Related Skills

Explore More Software Engineering Skills→
MFS-codeMFS-code
8

review

Review git diffs for SQL, LLM trust, and concurrency risks.

Community
Advanced
zz8011zz8011

review

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

Community
Intermediate
yanochka11yanochka11

review

Analyze repository diffs to identify defects, security risks, and structural problems.

Community
Advanced
ajsai47ajsai47
11

review

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

Community
Advanced