review

Review pull request diffs for SQL safety and LLM trust boundary issues.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/billydeeii136/black-opps-gstack --skill review-billydeeii136
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/billydeeii136/black-opps-gstack/tree/main/review
Command: npx skills add https://github.com/billydeeii136/black-opps-gstack --skill review-billydeeii136

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Read, Edit, Write, Grep, Glob, Agent, AskUserQuestion, WebSearch, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the pre-landing code review process, providing automated checks for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues.

Core Features & Use Cases

  • Automated Review: Analyze diff against the base branch for potential issues.
  • SQL Safety: Detect SQL injection vulnerabilities.
  • LLM Trust: Identify potential issues with LLM-generated code.
  • Use Case: Use this Skill when you are asked to "review this PR", "code review", "pre-landing review", or "check my diff".

Quick Start

To review a pull request, invoke the 'review' skill and specify the PR number.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate a pre-landing code review for a pull request?

Automating a pre-landing code review involves analyzing a pull request diff against its base branch to detect SQL injection vulnerabilities, LLM trust boundary violations, and structural issues before the code lands in the repository.

What is an LLM trust boundary violation in AI-generated code?

An LLM trust boundary violation occurs when AI-generated code bypasses established security parameters. A pre-landing code review identifies these violations to ensure AI-generated code integrates safely within your repository's established trust boundaries.

How do I check my diff for SQL injection vulnerabilities before merging?

To check your diff for SQL injection vulnerabilities, analyze the pull request changes against the base branch. This review process detects SQL safety issues and other structural flaws prior to landing the code.

Can I use this code review tool for AI-generated code in my repository?

Yes, this code review tool is applicable to PR review workflows in code repositories where AI-generated code is involved. It specifically detects conditional side effects and LLM trust boundary violations during the pre-landing review process.

What do I need to run a PR review with SQL safety checks?

Running a PR review with SQL safety checks requires a code repository environment with access to Bash, Read, Edit, Write, Grep, and Glob tools, along with a specified pull request number to analyze the diff.

Does this pre-landing review detect conditional side effects in pull requests?

Yes, the pre-landing review detects conditional side effects in pull requests by analyzing the diff against the base branch. It checks for SQL safety, LLM trust boundary violations, and other structural issues before code lands.