review

Analyze code diffs for SQL safety, LLM trust boundary violations, and race conditions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gstack, CLAUDE.md, git, python, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of code review, identifying potential issues such as SQL safety, LLM trust boundary violations, race conditions, and other structural issues, thereby speeding up the code review process and reducing human error.

Core Features & Use Cases

  • Automated Code Review: Analyze code diffs for SQL safety, LLM trust boundary violations, race conditions, and other structural issues.
  • Pre-Landing Review: Run before merging or landing code changes to catch issues early.
  • Use Case: When a developer wants to review a pull request or code changes, this Skill can be used to automatically check for potential issues without manual analysis.

Quick Start

Use the /review skill to automatically review the code changes in your current pull request.

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 SQL safety and race conditions in a pull request?

Automated code review analyzes diffs to detect SQL safety issues, race conditions, and structural problems. It checks code changes before landing to catch potential issues early without manual analysis.

What is an LLM trust boundary violation and how can I detect it in code changes?

An LLM trust boundary violation occurs when untrusted inputs cross security perimeters. Automated code review identifies these violations by analyzing code diffs for structural issues, ensuring safe integration of LLM components.

How do I run a pre-landing code review on my current pull request?

Run a pre-landing code review by executing the review command in your pull request directory. The skill analyzes your current code diffs to identify potential issues before merging changes.

Do I need the gstack framework and Python to run automated code analysis?

Yes, automated code analysis requires the gstack framework, Python, and git installed in your environment. These dependencies provide the necessary infrastructure for analyzing code diffs and detecting structural issues.

What structural issues can automated code review detect before merging code?

Automated code review detects SQL safety issues, LLM trust boundary violations, race conditions, and other structural problems. It analyzes code diffs to identify these issues during pre-landing reviews.

Can I use automated code analysis for quality assurance outside of pre-landing review?

Automated code analysis is designed for pre-landing code reviews to enhance quality and security. While primarily used before merging, it can analyze any code diff to identify structural issues.