review

Analyze branch diffs for SQL safety and trust boundary issues.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/shihwesley/shihwesleys-harness --skill review-shihwesley
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/shihwesley/shihwesleys-harness/tree/main/skills/gstack/review
Command: npx skills add https://github.com/shihwesley/shihwesleys-harness --skill review-shihwesley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the pre-landing PR review workflow by analyzing diffs against the base branch to surface structural issues, safety gaps, and trust boundary concerns.

Core Features & Use Cases

  • Diff-analysis against origin/main to identify SQL safety risks, data integrity issues, and potential side effects.
  • Two-pass review framework (CRITICAL, INFORMATIONAL) to guide automated fixes and human discussion.
  • Greptile triage integration and TODOS cross-referencing to coordinate triage and project planning.

Quick Start

Submit the current PR branch to the /review workflow to generate a structured report with actionable findings.

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 and trust boundaries?

Pre-landing PR review is automated by analyzing branch diffs against origin/main to identify SQL safety risks, LLM trust boundary issues, and potential side effects. A two-pass framework classifies findings as CRITICAL or INFORMATIONAL to propose actionable fixes.

What is a two-pass review framework for diff triage?

A two-pass review framework for diff triage categorizes structural issues found in code changes into CRITICAL or INFORMATIONAL levels. This classification guides automated fixes and human discussion by prioritizing safety gaps and trust boundary concerns.

How does Greptile triage integrate with PR diff analysis?

Greptile triage integrates with PR diff analysis by cross-referencing identified structural issues and TODOS tracking. This coordination surfaces actionable items across the project to align triage and project planning directly within the review workflow.

Can I use this to check potential side effects before landing a PR?

Yes, you can check potential side effects before landing a PR by submitting your current branch to the review workflow. It analyzes the diff against the base branch to surface data integrity issues and structural safety gaps.

What is the best way to classify PR findings for human discussion?

The best way to classify PR findings for human discussion is applying a two-pass review framework that categorizes structural issues into CRITICAL or INFORMATIONAL levels, proposing actionable fixes while coordinating triage through TODOS cross-referencing.

Does automated PR review work without additional dependencies?

Automated PR review operates without external dependencies by analyzing branch diffs directly against origin/main. It focuses on identifying SQL safety risks and LLM trust boundaries through its internal two-pass review framework.