skills.rest
ComputerConnection
ComputerConnectionCOMMUNITY
Explore all skills by this author →
GitHub

review

Detect structural risks in PR diffs for SQL safety and trust boundaries.

Updated Mar 31, 2026
Search Tags:#review#code-quality#pull-request#pr-review#diff-analysis#sql-safety
One-click install
npx skills add https://github.com/ComputerConnection/zach-pack --skill review-computerconnection
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/ComputerConnection/zach-pack/tree/main/skills/gstack-review
Command: npx skills add https://github.com/ComputerConnection/zach-pack --skill review-computerconnection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR review requires examining code diffs against the base branch to identify structural issues, SQL safety concerns, trust-boundary violations, and unintended side effects before merging. This skill provides a repeatable review workflow and actionable guidance for reviewers and developers.

Core Features & Use Cases

  • Analyzes diffs for SQL safety, trust boundaries, and potential conditional side effects.
  • Guides reviewers with a structured, repeatable checklist and actionable fixes.
  • Supports proactive recommendations to improve PR quality before land/release.

Quick Start

Provide the PR diff or description and let the skill generate a structured pre-landing review.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate a pull request review to check SQL safety and side effects?▼

Automating a pull request review involves analyzing PR diffs to detect SQL safety risks, trust-boundary violations, and unintended side effects. Providing the diff and PR metadata generates a structured checklist with actionable fixes for pre-landing checks.

What is diff-aware code analysis for pre-landing reviews?▼

Diff-aware code analysis evaluates structural risks in PR patches by comparing them against the base branch. It detects SQL safety issues, trust-boundary violations, and unintended side effects, providing a repeatable checklist and actionable fixes for reviewers.

How do I run a structured code review on a patch diff?▼

Running a structured code review requires providing the patch diff and PR metadata. The workflow then outputs a repeatable checklist that detects structural risks, trust-boundary violations, and side effects, guiding reviewers with actionable fixes.

Can I use automated diff analysis for merge checks on any pull request?▼

Automated diff analysis applies to pre-landing reviews, code reviews, and merge checks when evaluating diffs, PRs, or patches. It requires access to diff context and PR metadata to provide actionable recommendations regarding SQL safety and side effects.

What are the limitations of automated PR review for trust boundaries?▼

Automated PR review for trust boundaries is limited to examining structural risks within the provided diff context and PR metadata. It cannot evaluate runtime behavior or external factors outside the patch, focusing solely on SQL safety and potential side effects.

Related Skills

Explore More Software Engineering Skills→
akiyoshiakiyoshi

gstack-review

Analyze diffs against PR descriptions and plan files for structural issues.

Community
Advanced
shaythegay13shaythegay13

review

Analyze PR diffs for SQL safety, LLM trust boundaries, and side effects.

Community
Advanced
samChang72samChang72
1

code-review

Automates code reviews to detect bugs, style violations, and performance issues in submissions via static analysis tools.

Community
Intermediate
chf3198chf3198

github-review-merge-admin

Validate GitHub pull request approvals, status checks, and merge readiness.

Community
Intermediate