review

Analyze diffs against the base branch for SQL safety and trust boundary issues.

Updated Sep 10, 2024
One-click install
npx skills add https://github.com/TioSavich/UMEDCTA --skill review-tiosavich
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/TioSavich/UMEDCTA/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/TioSavich/UMEDCTA --skill review-tiosavich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR reviews often miss subtle issues hidden in diffs. This Skill analyzes diffs against the base branch to surface SQL safety issues, LLM trust boundary violations, and other structural problems before merge.

Core Features & Use Cases

  • Diff analysis against the base branch to surface SQL safety and data integrity concerns
  • LLM trust boundary checks to prevent unsafe prompt leakage and misuses
  • Proactive merge-readiness suggestions, including when to push back on changes
  • Structured, developer-friendly output that guides fixes and risk mitigation
  • Use Case: When a PR touches data access, ORMs, or text generation, run this skill to surface potential race conditions and unsafe patterns before landing

Quick Start

Run this skill on a PR to obtain a structured pre-landing review of the diff against the base branch.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate PR reviews for SQL safety and LLM trust boundary violations?

You can automate PR reviews by analyzing diffs against the base branch to surface SQL safety issues, LLM trust boundary violations, and conditional side effects. The review provides structured output guiding fixes and risk mitigation before merging.

What is pre-landing diff analysis and how does it prevent race conditions?

Pre-landing diff analysis checks changes against the base branch to identify potential race conditions and unsafe data access patterns. It proactively suggests merge-readiness actions and when to push back on changes before they land.

How do I run a code review on my current diff before merging?

Run a code review by prompting with phrases like "review this PR" or "check my diff". The skill uses deterministic tooling including Bash, Read, Edit, Grep, and Glob to perform structural checks and surface merge risks.

Does this automated code review work without external API dependencies?

Yes, automated code review works without external API dependencies. It relies entirely on deterministic tooling like Bash, Read, Edit, Write, Grep, Glob, and AskUserQuestion to perform checks against the base branch diff.

When should I use an automated diff analysis check on my pull request?

Use automated diff analysis when a PR touches data access, ORMs, or text generation. It is designed to surface potential race conditions and unsafe patterns specifically in these areas before landing your code.