review

Name: review
Availability: InStock
Author: Davirain

Review pre-landing pull requests for SQL safety and trust boundary issues.

Updated Mar 16, 2026

Search Tags:#quality assurance #code review #PR review #automated review #AI-assisted code analysis

Ready to run

npx skills add https://github.com/DaviRain-Su/sui-zig-rpc-client --skill review-davirain-su

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/DaviRain-Su/sui-zig-rpc-client/tree/main/.agents/skills/gstack-review
Command: npx skills add https://github.com/DaviRain-Su/sui-zig-rpc-client --skill review-davirain-su

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the pre-landing code review process, identifying potential issues such as SQL safety, trust boundary violations, and structural problems, saving time and reducing manual effort.

Core Features & Use Cases

Automated Code Review: Analyze code diffs against the base branch for safety and structural issues.
Trust Boundary Checks: Ensure that code changes do not violate AI-assisted trust boundaries.
Code Quality Analysis: Identify common coding issues like SQL injection risks, data races, and more.
Use Case: Before merging a pull request, use this Skill to automatically check for common issues that could be overlooked during manual review.

Quick Start

Use the review skill to perform a code review for the current PR branch.

Frequently Asked Questions about review

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

FAQPage Schema

How do I automate PR code review for SQL safety and trust violations?▼

Automated PR code review identifies SQL safety risks and trust boundary violations by analyzing Git diffs against the base branch. This process saves time and reduces manual effort by catching common structural and security issues before landing.

What are AI-assisted trust boundary checks in pull requests?▼

AI-assisted trust boundary checks ensure that code changes in a pull request do not violate established trust boundaries. This automated analysis reviews Git diffs to detect potential security risks and structural problems before merging.

How does automated code review detect SQL injection risks in a Git diff?▼

Automated code review detects SQL injection risks by analyzing Git diffs against the base branch. It identifies SQL safety issues, data races, and other code-related problems within the changes before the pull request is merged.

Do I need gstack tooling to perform automated pre-landing code review?▼

Yes, gstack tooling is required to perform automated pre-landing code review. The process assumes the presence of gstack along with relevant configuration files and Git repository access to analyze diffs for safety and structural issues.

Can I use this automated review for checking data races and code quality issues?▼

Yes, you can use automated review to check for data races and code quality issues. It analyzes pull request diffs to identify common coding problems, SQL safety risks, and trust boundary violations before code is merged.

What is the best way to check pre-landing pull requests for structural problems?▼

The best way to check pre-landing pull requests for structural problems is using automated code review. It analyzes Git diffs to identify SQL safety risks, trust boundary violations, and structural issues, reducing manual effort.