skills.rest
GTC6244
GTC6244COMMUNITY
Explore all skills by this author →
GitHub

review

Analyze code diffs against the base branch for SQL safety and trust boundary issues.

Updated Apr 5, 2026
Search Tags:#review#code-quality#pull-request#pr-review#diff-analysis#data-safety#llm-trust
One-click install
npx skills add https://github.com/GTC6244/ToolBridge --skill review-gtc6244
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/GTC6244/ToolBridge/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/GTC6244/ToolBridge --skill review-gtc6244

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Review skill provides a structured, automated assessment of code diffs to surface correctness, safety, and quality issues before merging.

Core Features & Use Cases

  • Analyzes diffs for SQL safety, LLM trust boundaries, conditional side effects, and other structural issues; Proactively suggests fixes and next steps. Use when evaluating a PR or code diff.
  • Generates a concise completion report and recommended actions to ship or revert changes.

Quick Start

Start a review by invoking the skill on a branch with changes to see an automated report.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate PR review for data safety and LLM trust boundary violations?▼

Automated PR review analyzes branch diffs to surface data safety, LLM trust boundary violations, and structural issues. It identifies SQL safety risks and conditional side effects, then outputs actionable recommendations and a completion status for developers to follow.

What is the best way to analyze code diffs for SQL safety before merging?▼

Analyzing code diffs for SQL safety involves evaluating the changes against the base branch to detect risk patterns. The review process identifies potential SQL safety issues and generates a concise plan with suggested fixes and routing guidance.

Can I use automated code review to identify conditional side effects in pull requests?▼

Automated code review can identify conditional side effects in pull requests by analyzing the structural changes in the diff. It proactively surfaces these structural issues alongside LLM trust boundary violations and generates recommended actions to ship or revert changes.

How does diff analysis handle structural issues in a pull request?▼

Diff analysis handles structural issues by comparing the branch changes against the base branch to detect risk patterns. It surfaces structural issues, provides routing guidance, and outputs a concise completion report with suggested fixes for developers.

What pull request review limitations exist for LLM trust boundary checks?▼

Pull request review for LLM trust boundary checks focuses on surfacing violations through diff analysis against the base branch. It applies across codebases to identify trust boundary issues and outputs actionable recommendations, though it requires a clear diff to analyze.

Do I need a specific codebase structure to run automated diff analysis for PR review?▼

Automated diff analysis for PR review applies across codebases without requiring a specific structure. It evaluates the diff against the base branch to surface structural issues, SQL safety, and LLM trust boundary violations, generating a completion report and suggested fixes.

Related Skills

Explore More Software Engineering Skills→
avvaleavvale

commit-pr

Commit changes, push to a feature branch, and create a GitHub Pull Request.

Official
Advanced
zz8011zz8011

review

Analyze PR diffs for SQL safety, LLM trust boundary violations, and conditional side effects.

Community
Intermediate
SjdjdiejdrirhdkjejSjdjdiejdrirhdkjej

optimization-phase

Run post-implementation quality gates and generate reports before release.

Community
Advanced
aporto-techaporto-tech

gstack-review

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

Official
Advanced