review

Detect SQL safety, LLM trust, and side-effect risks in PR diffs.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/zaeem-rafiq/tatheer-swift-sdk --skill review-zaeem-rafiq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/zaeem-rafiq/tatheer-swift-sdk/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/zaeem-rafiq/tatheer-swift-sdk --skill review-zaeem-rafiq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR review and gatekeeping for code changes, catching SQL safety issues, LLM trust boundaries, and side-effect risks before merging.

Core Features & Use Cases

  • Two-pass check: critical issues first (SQL safety, LLM trust) and informational items second.
  • Automated fix-first workflow: auto-fixes for mechanical issues; batched questions for human input.
  • Greptile integration: triage comments from reviewers; escalation flows.
  • Step-by-step guidance with an "AskUserQuestion" structured format for decisions.

Quick Start

Run the /review workflow on the current branch to begin a guided PR audit.

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 to catch SQL safety and side-effect risks before merging?

Automated PR review detects SQL safety issues, LLM trust violations, and side-effect risks in diffs. It runs a two-pass check prioritizing critical issues first, then informational items, providing a clear actionable report before you merge.

What is a two-pass diff analysis for pull requests?

Two-pass diff analysis evaluates pull request changes in stages: critical SQL safety and LLM trust violations are checked first, followed by informational items. This structured gatekeeping ensures severe merge blockers are caught before minor styling or informational feedback is reviewed.

How do I auto-fix mechanical PR issues while escalating complex decisions to reviewers?

A fix-first workflow auto-fixes mechanical PR issues automatically while batching complex decisions into structured AskUserQuestion prompts. This routes trivial corrections to automation and escalates only critical triage comments to human reviewers.

Can I use Greptile integration to triage reviewer comments on a PR branch?

Greptile integration supports triaging reviewer comments and escalation flows during PR review. When invoked on a PR branch, the assistant captures telemetry and routes triage comments to ensure proper governance of code changes.

Does this pre-landing PR review work without external dependencies?

Yes, the pre-landing PR review operates with no external dependencies required. It invokes directly on your current PR branch to analyze diffs, detect risks, and produce a structured governance report without needing additional packages or components.

What are the limitations of automated diff analysis for LLM trust boundaries?

Automated diff analysis for LLM trust boundaries is limited to detecting predefined risk patterns in code changes. It cannot evaluate runtime behavior or complex architectural context, meaning human input via structured prompts is still required for nuanced governance decisions.