review

Review pull request diffs against main for SQL and LLM trust issues.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/tpgordon8/Pet-App --skill review-tpgordon8
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/tpgordon8/Pet-App/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/tpgordon8/Pet-App --skill review-tpgordon8

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the initial review of code changes in a Pull Request, identifying critical structural issues before they reach human reviewers.

Core Features & Use Cases

  • Automated Code Analysis: Scans code diffs against the main branch for common pitfalls like SQL injection, race conditions, and LLM trust boundary violations.
  • Structured Feedback: Provides categorized findings (Critical and Informational) based on a predefined checklist.
  • Use Case: Before merging a new feature, run this Skill to catch potential security vulnerabilities or data integrity issues, ensuring higher code quality and faster review cycles.

Quick Start

Run the review skill to analyze the current branch's changes against main.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate code review for pull requests before they reach human reviewers?

Automated code review scans your pull request diffs against the main branch to identify critical structural issues like SQL safety and LLM trust boundary violations before human review. It categorizes findings into blocking and informational alerts based on a predefined checklist.

What security vulnerabilities can pre-landing code analysis catch in a PR?

Pre-landing code analysis catches security vulnerabilities including SQL injection risks, race conditions, and LLM trust boundary violations. It scans code diffs to identify these critical structural problems and categorizes them for blocking or informational review.

How do I run a code quality check on my current branch before merging?

To run a code quality check, execute the review skill to analyze your current branch's changes against the main branch. It automatically identifies potential data integrity issues and structural problems, providing categorized feedback.

Can I use automated code review to detect LLM trust boundary violations in my code?

Yes, automated code review specifically detects LLM trust boundary violations by scanning your pull request diffs. It identifies these structural problems along with SQL safety issues and conditional side effects, categorizing them for review.

Does pre-landing code review replace the need for manual PR analysis?

Pre-landing code review does not replace manual PR analysis, but automates the initial review to catch critical issues like SQL injection and race conditions early. It provides structured feedback to ensure higher code quality and faster human review cycles.

What is the best way to identify SQL safety issues in a pull request diff?

The best way to identify SQL safety issues is running automated pre-landing code review on your pull request diff. It flags SQL safety problems alongside conditional side effects and LLM trust boundary violations, categorizing findings into critical and informational alerts.