skills.rest
mattothomas
mattothomasCOMMUNITY
Explore all skills by this author →
GitHub

review

Analyze PR diffs for SQL safety, LLM trust boundary violations, and side-effect risks.

Updated Mar 28, 2026
Search Tags:#diff#code-review#pr-review#plan-review#sql-safety#pre-landing#llm-boundaries
One-click install
npx skills add https://github.com/mattothomas/sp26_hackpsu --skill review-mattothomas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/mattothomas/sp26_hackpsu/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/mattothomas/sp26_hackpsu --skill review-mattothomas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill performs a pre-landing PR review by analyzing diffs against the base branch for SQL safety, LLM trust boundary violations, and structural issues. It helps catch risky changes before merging and suggests actions to keep code safe.

Core Features & Use Cases

  • Diff-based safety analysis: checks SQL interactions for potential injections or unsafe patterns against the base branch.
  • LLM trust boundary checks: detects prompts, data leakage risks, and boundary violations in review comments and logic.
  • Structural checks: flags conditional side effects, ambiguous refactors, and potential merge hazards; supports proactive suggestions when merges are imminent.
  • Plan-aware guidance: integrates with existing plan/TODOS workflows to surface actionable steps for reviewers.

Quick Start

Upload or reference the PR diff and run the /review workflow to start the audit.

Frequently Asked Questions about review

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

FAQPage Schema
How do I check a PR diff for SQL injection risks before merging?▼

To check a PR diff for SQL injection risks before merging, you can run a pre-landing review that performs static analysis on the diff to identify and report SQL safety issues against the base branch.

What is an LLM trust boundary violation in code review?▼

An LLM trust boundary violation in code review occurs when prompts or data leakage risks bypass security perimeters. This Skill detects these boundary violations in review comments and logic during diff analysis.

How do I review a Git branch diff for side-effect risks?▼

To review a Git branch diff for side-effect risks, you run a structural audit that flags conditional side effects, ambiguous refactors, and potential merge hazards against the base branch before landing.

Can I use static checks to enforce deterministic behavior for code reviews?▼

Yes, you can use static checks to enforce deterministic behavior for code reviews. This Skill applies policy-driven gating and diff analysis to ensure deterministic behavior and safe merges across Git branches.

Does this pre-landing review tool integrate with plan and TODO workflows?▼

Yes, this pre-landing review tool integrates with plan and TODO workflows. It provides plan-aware guidance that surfaces actionable steps for reviewers by analyzing the PR diff against existing plans.

Related Skills

Explore More Software Engineering Skills→
twikustwikus
3

create-pr

Create GitHub pull requests from the current branch using gh CLI.

Community
Intermediate
whd4whd4

review

Audit diffs for SQL safety, trust boundary violations, and side effects.

Community
Advanced
vm0-aivm0-ai
1.1k

pull-request

Automate GitHub pull-request creation, merging with CI validation, and comments.

Official
Intermediate
ajsai47ajsai47
11

review

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

Community
Advanced