review

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

1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/geoffreywoo/clawfable --skill review-geoffreywoo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/geoffreywoo/clawfable/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/geoffreywoo/clawfable --skill review-geoffreywoo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diff-heavy PRs often hide SQL safety issues, trust boundary violations in LLM prompts, and subtle side effects that slip into landings. This Skill performs a pre-landing PR review by analyzing the diff against the base branch and surfacing these structural risks so you can decide what to fix before merging.

Core Features & Use Cases

  • Pre-landing PR review that analyzes diffs for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues.
  • Proactively suggest fixes or questions when you are about to merge code changes, helping teams catch issues early.
  • Generates actionable feedback and recommendations that can be loaded into developer context during reviews.

Quick Start

Trigger the review workflow on a branch to start the 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 code review for PR diffs before merging?

Automated PR review analyzes branch diffs against the base branch to surface SQL safety risks, LLM trust boundary violations, and conditional side effects. It returns actionable guidance with file-level references and concrete next steps to fix issues before landing.

What structural risks should I check for when reviewing a PR diff?

PR diff review should check for SQL safety risks, LLM trust boundary violations, and subtle conditional side effects. Automated pre-landing checks surface these structural issues so you can catch problems early and decide what to fix before merging code changes.

Can I run automated QA checks on multi-branch workflows?

Automated QA checks support multi-branch workflows by analyzing PR diffs against the base branch to provide automated feedback. This speeds up merge readiness by generating actionable recommendations that can be loaded directly into developer context during reviews.

How do I detect LLM trust boundary violations in my code changes?

Detecting LLM trust boundary violations involves analyzing PR diffs to identify where prompt inputs cross security boundaries. Automated pre-landing reviews surface these structural risks alongside SQL safety issues and conditional side effects with file-level references.

What is the best way to catch SQL safety issues before landing code?

Catching SQL safety issues before landing code requires analyzing PR diffs against the base branch. Automated review workflows surface these risks proactively, generating actionable feedback and recommendations to help teams fix issues early before merge.

Does automated PR review work without external dependencies?

Automated PR review operates without external dependencies, analyzing diffs directly to surface structural risks. It provides actionable guidance with file-level references and concrete next steps, fitting seamlessly into code reviews and pre-landing checks.