review

Analyze code changes for SQL safety, trust boundary violations, and structural issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of code review, allowing you to quickly identify potential issues and maintain code quality without manual inspection.

Core Features & Use Cases

  • Automated Code Review: Analyze code changes for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues.
  • Proactive Suggestions: Suggest potential issues before code is merged or landed, helping to prevent common mistakes.
  • Use Case: Imagine you're about to merge a pull request with significant changes. Use this Skill to review the code changes, identify potential issues, and make necessary adjustments before merging.

Quick Start

Run the "review this PR" command to automatically review the code changes in the 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 to identify common software development issues?

Automated code review analyzes code changes to detect SQL safety risks, LLM trust boundary violations, and structural issues. It scans your pull request changes to pinpoint potential problems and proactively suggest fixes before merging.

What's the best way to review a pull request for potential issues before merging?

The best way to review a pull request before merging is running an automated code review command. This process analyzes code changes, identifies potential issues like conditional side effects, and suggests necessary adjustments to maintain software quality.

Does automated code review detect SQL safety and LLM trust boundary violations?

Yes, automated code review detects SQL safety issues and LLM trust boundary violations. It analyzes code changes specifically looking for these structural issues, along with conditional side effects, to ensure software development quality and security.

What environment do I need to run automated code review on code changes?

You need an environment supporting Bash, Read, Edit, Write, Grep, Glob, Agent, AskUserQuestion, and WebSearch capabilities. This setup allows the automated review process to thoroughly analyze code changes and suggest accurate fixes.

Why should I use automated code review instead of manual inspection?

Automated code review saves time and ensures quality by quickly identifying potential issues without manual inspection. It proactively analyzes code changes for common mistakes and suggests fixes, which is particularly useful in time-consuming software development workflows.

When do I need automated code review in my software development workflow?

You need automated code review when merging pull requests with significant changes in software development environments where manual inspection is time-consuming. It proactively identifies potential issues and suggests fixes before code is landed.