skills.rest
shaneholloman
shanehollomanCOMMUNITY
Explore all skills by this author →
GitHub

review

Analyzes code diffs to detect SQL safety, LLM trust boundary violations, and conditional side effects in PRs before merging.

Updated Mar 19, 2026
Search Tags:#pr-review#diff-analysis#design-checklist#todo-management#sql-safety#llm-trust#greptile-triage
One-click install
npx skills add https://github.com/shaneholloman/ship --skill review-shaneholloman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/shaneholloman/ship/tree/main/review
Command: npx skills add https://github.com/shaneholloman/ship --skill review-shaneholloman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR reviews are time-consuming and error-prone, often missing subtle issues in diffs. This Skill automates the process by examining diffs against the base branch to identify SQL safety concerns, LLM trust boundary violations, and potentially risky side effects before merging.

Core Features & Use Cases

  • Automated, structured PR analysis across SQL safety, data integrity, and prompt safety boundaries.
  • Two-pass review workflow with auto-fix of mechanical issues and batch guidance for human input on ambiguous items.
  • Works with design and Greptile triage checklists to surface actionable findings and maintain code quality.

Quick Start

Run the /review workflow on a target PR to initiate an automated, safety-focused pre-landing 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 reviews for SQL safety and LLM trust boundaries?▼

Automated pre-landing PR reviews analyze code diffs against the base branch to identify SQL safety concerns, LLM trust boundary violations, and risky side effects before merging.

What is a two-pass review workflow for analyzing code diffs?▼

A two-pass review workflow automates pre-landing PR analysis by first auto-fixing mechanical issues, then providing batch guidance for human input on ambiguous items.

How do I check my code diffs for SQL safety concerns before merging?▼

You can check code diffs for SQL safety concerns by applying automated SQL checks and design checklists against the base branch diff to surface actionable findings.

Can I use Greptile triage to surface actionable findings in a pre-landing review?▼

Yes, the pre-landing review workflow works with Greptile triage checklists to surface actionable findings and maintain code quality during diff analysis.

What is the best way to manage TODOs and design checklists during a PR review?▼

The best way to manage TODOs and design checklists is using an automated review workflow that applies these tools to produce actionable feedback and maintain code safety.

Does automated PR review work without external dependencies?▼

Yes, the automated pre-landing PR review operates without dependencies, using internal tools and checklists to identify LLM trust boundary violations and conditional side effects.

Related Skills

Explore More Software Engineering Skills→
xinbenlvxinbenlv
8

retrieve-diff-from-commit

Retrieve unified diffs and commit metadata from local Git repositories.

Community
Intermediate
g4rcezg4rcez
48

review

Analyze diffs against the base branch and auto-fix mechanical issues during PR reviews.

Community
Advanced
lyh2lyh2

review

Analyze branch diffs for SQL safety, trust boundary, and side-effect issues.

Community
Advanced
beratcelik1beratcelik1
1

verification-loop

Run build, typecheck, lint, tests, security scans, and diff review for code changes.

Community
Intermediate