review

Analyze diffs against the base branch for SQL safety and trust boundary issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR review involves surfacing risks and quality gaps before merging. This skill analyzes diffs against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues to help teams land safer changes.

Core Features & Use Cases

  • Diff-based safety and quality checks for pull requests to identify SQL vulnerabilities, data integrity concerns, and unintended side effects.
  • LLM trust boundary protection by validating prompts, routing, and risk exposures before changes are accepted.
  • Proactive merge guidance and actionable next steps to help engineers decide when a PR is merge-ready.

Quick Start

Tell me to review a PR, and I will analyze the diff against the base branch for safety risks and guidance.

Frequently Asked Questions about review

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

FAQPage Schema
How do I run a pre-landing code review for SQL safety and side effects?

Pre-landing PR review analyzes your pull request diff against the base branch to detect SQL safety issues, LLM trust boundary violations, and conditional side effects before merging. It outputs deterministic findings and recommendations to guide merge readiness.

What is LLM trust boundary validation in a pull request?

LLM trust boundary validation in a pull request checks prompts, routing, and risk exposures before changes are accepted. It prevents unintended LLM trust violations by proactively identifying structural issues in the diff against the base branch.

Can I use this diff analysis to check SQL vulnerabilities before merging?

Yes, you can use diff analysis to check SQL vulnerabilities before merging. It evaluates pull request diffs against the base branch to identify SQL safety issues, data integrity concerns, and unintended side effects to help teams land safer changes.

How do I get merge readiness guidance after a code review?

Merge readiness guidance is generated after code review by outputting deterministic findings, logging outcomes for telemetry, and providing actionable next steps. This helps engineers decide when a pull request is safe to land.

Does this pre-landing review work with the Hermes gstack workflow?

Yes, this pre-landing review works across repositories in the Hermes gstack workflow. It applies diff-based safety and quality checks for pull requests to identify SQL vulnerabilities and LLM trust boundary violations within that environment.