review

Analyze code diffs for SQL safety and trust boundary issues.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/joeylife94/gstack-2026-03 --skill review-joeylife94
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/joeylife94/gstack-2026-03/tree/main/review
Command: npx skills add https://github.com/joeylife94/gstack-2026-03 --skill review-joeylife94

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Read, Edit, Write, Grep, Glob, Agent, AskUserQuestion, WebSearch, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the pre-landing PR review process, helping identify and mitigate common issues before code is merged, reducing the time spent on manual code reviews.

Core Features & Use Cases

  • Automated Code Analysis: Analyzes diffs against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues.
  • Intelligent Suggestions: Proactively suggests when a review is needed, helping to catch potential issues early.
  • Customizable Checks: Allows users to configure the specific checks that should be performed on their PRs.

Quick Start

Run /review on your branch to automatically check your PR for common issues.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate PR code review for SQL safety and side effects?

You can automate PR code review by running a command on your branch to analyze code diffs against the base branch. This process detects SQL safety issues, LLM trust boundary violations, and conditional side effects before merging.

What is the best way to check code diffs for common issues before merging?

The best way to check code diffs before merging is using automated checks that analyze your branch against the base. This catches structural issues, side effects, and boundary violations early in the collaborative coding workflow.

Can I configure specific automated checks for my PR analysis?

Yes, you can configure the specific checks performed on your PRs. Customizable checks allow you to target exact issues like SQL safety, LLM trust boundaries, and conditional side effects based on your project requirements.

How does automated code review handle collaborative workflows with multiple contributors?

Automated code review handles collaborative workflows by proactively suggesting when a review is needed and checking diffs for common issues. This ensures consistent code quality before merging when multiple contributors are working together.

When do I need automated checks for LLM trust boundary violations?

You need automated checks for LLM trust boundary violations when your code diffs involve integrating or relying on large language model outputs. Running a pre-landing review identifies and mitigates these boundary issues before code is merged.

Does automated PR analysis work without manual code reviews?

Automated PR analysis reduces time spent on manual code reviews but does not entirely replace them. It identifies common issues like SQL safety and conditional side effects, allowing manual review to focus on complex logic.