review

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

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/Liambiswell20-tech/Bolus-Brain --skill review-liambiswell20-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Liambiswell20-tech/Bolus-Brain/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/Liambiswell20-tech/Bolus-Brain --skill review-liambiswell20-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR review is automated to analyze diffs against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues that tests may miss.

Core Features & Use Cases

  • Analyzes PR diffs to detect SQL safety risks such as unsafe string interpolation, race conditions, or improper validations.
  • Ensures LLM output trust by validating generated data and ensuring boundaries are respected before merging.
  • Supports a two-pass review workflow with clear escalation paths, checklists, and a fix-first approach.
  • Integrates with Greptile triage for line- and top-level PR comments to surface actionable issues.

Quick Start

Run the review workflow on your current branch to start a pre-landing PR review.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate pre-landing PR review for SQL safety?

Automated pre-landing PR review analyzes branch diffs against the base branch to detect SQL safety risks like unsafe string interpolation, ensuring validation before merging.

What is a two-pass PR review workflow with fix-first guidance?

A two-pass PR review workflow with fix-first guidance surfaces risks in initial passes and provides actionable remediation steps, integrating checklists and Greptile triage for comments.

How do I validate LLM trust boundaries in a pull request diff?

Validating LLM trust boundaries in a pull request diff involves checking generated data and ensuring boundary violations are detected and resolved before code merges.

Can I detect conditional side effects and structural issues that tests miss?

Yes, automated diff analysis can detect conditional side effects and structural issues that tests miss by evaluating code changes against the base branch for risks.

Does the PR review workflow integrate with Greptile triage for comments?

Yes, the PR review workflow integrates with Greptile triage to surface actionable issues through both line-level and top-level pull request comments.

When do I need to run a pre-landing review on my current branch?

Run a pre-landing review on your current branch to analyze SQL safety, LLM trust boundaries, and conditional side effects before merging code changes into the base branch.