review

Analyze branch diffs for SQL safety risks and LLM trust boundary violations.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/bizzybae/qstack --skill review-bizzybae
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/bizzybae/qstack/tree/main/gstack-original/review
Command: npx skills add https://github.com/bizzybae/qstack --skill review-bizzybae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes diffs against the base branch to surface SQL safety issues, LLM trust boundary warnings, and structural problems in pre-landing PRs.

Core Features & Use Cases

  • Detects potential SQL safety risks in code diffs and data handling changes.
  • Flags LLM trust boundary violations and risky side effects before merging.
  • Suggests actionable improvements and review focus for fast, high-quality landings.

Quick Start

Run the review skill on the current branch to evaluate the PR against the base, surfacing critical issues before merging.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate PR diff review for SQL safety risks?

Automated PR diff review for SQL safety risks analyzes the current branch diff against the base branch to identify data handling vulnerabilities. It surfaces potential SQL safety issues in code changes before merging, providing prioritized findings and remediation suggestions.

What are LLM trust boundary violations in pre-merge code?

LLM trust boundary violations in pre-merge code occur when changes introduce risky side effects or unauthorized trust levels for language model operations. The review process flags these boundary warnings in the diff to ensure safe integration before landing.

How do I run pre-landing checks for structural issues in PRs?

Pre-landing checks for structural issues in PRs evaluate the current branch against the base branch to detect code anomalies. Running an automated review surfaces these structural problems with actionable improvements for fast, high-quality landings.

Does automated PR review work for merge readiness checks?

Automated PR review works for merge readiness checks by analyzing the branch diff to identify SQL safety risks, LLM trust boundary violations, and structural problems. It outputs prioritized findings to determine if the code is ready for a high-quality landing.

What is the best way to identify risky side effects in a code diff?

The best way to identify risky side effects in a code diff is to run an automated review against the base branch. This process flags LLM trust boundary violations and structural issues, providing remediation suggestions for actionable next steps before merging.