skills.rest
garrytan
garrytanCOMMUNITY
Explore all skills by this author →
Website𝕏@garrytanGitHub

review

Analyze Git branch diffs against main for SQL injection and race conditions.

127k|19.1k|Updated Mar 11, 2026
Search Tags:#git#developer tools#quality assurance#code review#pr review#greptile
One-click install
npx skills add https://github.com/garrytan/gstack --skill review-garrytan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/garrytan/gstack/tree/main/review
Command: npx skills add https://github.com/garrytan/gstack --skill review-garrytan

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of reviewing code changes before they are merged, identifying critical structural issues that automated tests might miss.

Core Features & Use Cases

  • Pre-landing Code Analysis: Analyzes diffs against the main branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural problems.
  • Greptile Triage: Integrates with Greptile to classify and act upon automated review comments.
  • Use Case: Before merging a new feature, run this Skill to catch potential bugs related to data safety or unexpected LLM behavior, ensuring higher code quality and preventing production issues.

Quick Start

Run the review skill to analyze the current branch's diff 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 pre-landing code review on a Git branch?▼

Pre-landing code review analyzes your Git branch's diff against the main branch to identify critical structural issues before merging. It catches SQL injection vulnerabilities, LLM trust boundary violations, conditional side effects, and potential race conditions that automated tests might miss.

What structural problems should a PR review catch before merging?▼

A thorough PR review should catch critical structural problems like SQL injection vulnerabilities, LLM trust boundary violations, conditional side effects, and potential race conditions. These issues often slip past automated tests but cause severe production bugs and data safety failures.

Can I use Greptile to triage automated review comments on pull requests?▼

Yes, you can use Greptile to triage automated review comments on pull requests. Greptile integration classifies and acts upon automated comments generated during pre-landing code analysis, helping developers manage and resolve feedback efficiently.

Do I need any special dependencies to run automated code analysis on my Git diff?▼

No special dependencies are required to run automated code analysis on your Git diff. The review process operates independently using internal scripts and references to analyze the branch diff against main without external setup barriers.

What is the best way to prevent LLM trust boundary violations in new code?▼

The best way to prevent LLM trust boundary violations is running pre-landing code analysis on your Git branch diff before merging. This identifies unexpected LLM behavior and data safety issues early, ensuring higher code quality and preventing production problems.

Related Skills

Explore More Software Engineering Skills→
buihuulocbuihuuloc

merge-main

Merge the main branch into a feature branch with PowerShell.

Community
Advanced
fredericpoitevinfredericpoitevin

babysit

Triage PR comments, resolve conflicts, and stabilize CI until merge-ready.

Community
Intermediate
MFS-codeMFS-code
8

review

Review git diffs for SQL, LLM trust, and concurrency risks.

Community
Advanced
ajsai47ajsai47
11

review

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

Community
Advanced