skills.rest
26mitch26
26mitch26COMMUNITY
Explore all skills by this author →
GitHub

review

Analyze code diffs for SQL safety and structural issues with gstack.

Updated Jun 11, 2026
Search Tags:#diff analysis#code review#PR review#gstack#pre-landing review
One-click install
npx skills add https://github.com/26mitch26/ai-mall --skill review-26mitch26
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/26mitch26/ai-mall/tree/main/.claude/skills/review
Command: npx skills add https://github.com/26mitch26/ai-mall --skill review-26mitch26

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a comprehensive pre-landing PR review, analyzing diffs against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. It helps identify potential issues before merging or landing code changes.

Core Features & Use Cases

  • Diff Analysis: Analyze diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues.
  • Code Review: Use when asked to "review this PR", "code review", "pre-landing review", or "check my diff".
  • Proactive Suggestion: Suggests review when the user is about to merge or land code changes.

Quick Start

Use the /review skill to perform a pre-landing review of this PR.

Frequently Asked Questions about review

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

FAQPage Schema
How do I perform a pre-landing code review on my PR diff?▼

A pre-landing code review analyzes your PR diff against the base branch to detect SQL safety issues, LLM trust boundary violations, and conditional side effects before merging. You can trigger this by running the /review command.

What structural issues can a diff analysis check before merging code?▼

Diff analysis checks for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. This helps identify potential problems in your code changes before they are merged or landed.

Do I need gstack to run an automated PR review?▼

Yes, you need gstack installed because the automated PR review is built on top of it. The Skill requires the gstack framework to function and analyze your code diffs properly.

Can I check for LLM trust boundary violations in my code changes?▼

Yes, you can check for LLM trust boundary violations by analyzing your code diff against the base branch. The review process identifies these violations along with SQL safety and conditional side effects.

When should I run a pre-landing review on my pull request?▼

You should run a pre-landing review when you are about to merge or land code changes. It can also be triggered proactively or used when you ask to review a PR, check a diff, or perform a code review.

Related Skills

Explore More Software Engineering Skills→
Chang-Shih-YungChang-Shih-Yung

review

Analyze diffs against the base branch for SQL safety and structural issues.

Community
Advanced
aporto-techaporto-tech

gstack-review

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

Official
Advanced
tunneleventunneleven

c4flow:pr-review

Process pull request comments and push code updates iteratively.

Community
Intermediate
ajsai47ajsai47
11

review

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

Community
Advanced