skills.rest
yocxy2
yocxy2COMMUNITY
Explore all skills by this author →
GitHub

review

Analyze git diffs for SQL safety, concurrency, and LLM trust boundary violations.

Updated Jul 26, 2026
Search Tags:#automation#git#code review#pull request#security#safety
One-click install
npx skills add https://github.com/yocxy2/gstack3 --skill review-yocxy2
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/yocxy2/gstack3/tree/main/review
Command: npx skills add https://github.com/yocxy2/gstack3 --skill review-yocxy2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill automates the critical pre-landing review process, catching structural issues, SQL safety violations, and trust boundary risks that human reviewers often miss.

Core Features & Use Cases

  • Critical Safety Analysis: Automatically scans for SQL injection, race conditions, and LLM trust boundary violations.
  • Fix-First Review: Applies mechanical fixes for identified issues and batches ambiguous findings into a single, clear user question.
  • Use Case: Before merging a complex PR, run this skill to ensure your code adheres to production safety standards, preventing bugs and security vulnerabilities from reaching the main branch.

Quick Start

Invoke the review skill to perform a comprehensive safety and structural analysis of the current pull request diff.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate pull request review for SQL injection and concurrency issues?▼

Automated pull request review analyzes git diffs against base branches to detect SQL injection, race conditions, and concurrency issues, applying mechanical fixes to ensure production safety before merging.

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

An LLM trust boundary violation occurs when untrusted input crosses into LLM processing without validation. Automated code review scans git diffs to identify these structural risks alongside SQL safety and concurrency issues.

How do I run automated safety checks on a git diff before merging?▼

Automated safety checks run by analyzing the git diff of your current pull request against its base branch, identifying structural issues, SQL safety violations, and trust boundary risks to prevent bugs from reaching production.

Do I need a configured gstack environment to run automated code review?▼

Yes, automated code review requires a configured gstack environment along with git and bash to execute safety checks, telemetry logging, and mechanical fixes on pull request diffs.

Can automated code review fix SQL safety issues or does it only report them?▼

Automated code review applies mechanical fixes for identified SQL safety and concurrency issues, batching any ambiguous findings into a single clear question for the user to resolve.

What are the limitations of automated structural code review for pull requests?▼

Automated structural code review focuses on mechanical safety violations like SQL injection and race conditions. It cannot assess business logic correctness and requires batching ambiguous findings for manual user resolution.

Related Skills

Explore More Software Engineering Skills→
timurgaleevtimurgaleev
5

review

Diagnose PR diffs for SQL safety and LLM trust boundary issues.

Community
Advanced
cosmixcosmix
53

ci-cd

Design and automate CI/CD pipelines for GitHub Actions, GitLab CI, and Jenkins.

Community
Advanced
GolferGeekGolferGeek

GitHub Workflow

Standardize GitHub branching, pull requests, code reviews, and CI/CD pipelines.

Community
Basic
ajsai47ajsai47
11

review

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

Community
Advanced