skills.rest
milo0914
milo0914COMMUNITY
Explore all skills by this author →
GitHub

review

Analyze git diffs for SQL safety, race conditions, and trust boundary violations.

Updated Aug 27, 2026
Search Tags:#automation#code review#pull request#safety#diff#gstack
One-click install
npx skills add https://github.com/milo0914/hermes-skills-backup --skill review-milo0914
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/milo0914/hermes-skills-backup/tree/main/review
Command: npx skills add https://github.com/milo0914/hermes-skills-backup --skill review-milo0914

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill automates the pre-landing review process, identifying structural issues, SQL safety risks, and trust boundary violations before code is merged.

Core Features & Use Cases

  • Automated Diff Analysis: Scans changes against the base branch for common pitfalls like race conditions and shell injection.
  • Proactive Guidance: Integrates with gstack to suggest improvements and ensure adherence to project-specific routing rules.
  • Use Case: Use this skill when you are ready to land a PR to ensure your changes are secure, performant, and consistent with the existing codebase.

Quick Start

Invoke the review skill to perform a comprehensive pre-landing analysis of your current diff.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate a pre-landing code review for my pull request?▼

Automated pre-landing code review scans your git diff against the base branch to detect SQL safety issues, race conditions, and shell injection before merging. It proactively identifies structural pitfalls and suggests improvements to ensure code is secure and performant.

What types of safety issues can automated diff analysis detect in a pull request?▼

Automated diff analysis detects SQL safety risks, race conditions, shell injection, and LLM trust boundary violations. It scans changes against the base branch to identify these common pitfalls and structural issues before code is merged into the existing codebase.

Do I need gstack infrastructure to run automated pre-landing code reviews?▼

Yes, executing automated pre-landing safety checks requires gstack infrastructure and standard git tooling. The review process integrates with gstack to suggest improvements and ensure adherence to project-specific routing rules during the diff analysis.

When should I run an automated diff analysis on my code changes?▼

Run automated diff analysis when you are ready to land a PR. Use this pre-landing review process to ensure your code changes are secure, performant, and consistent with the existing codebase, catching structural issues and trust boundary violations early.

Can automated code review check for LLM trust boundary violations in my git diff?▼

Yes, automated code review analyzes your git diff to detect LLM trust boundary violations. It scans changes against the base branch to identify these security risks alongside SQL safety issues and race conditions before your pull request is merged.

Related Skills

Explore More Software Engineering Skills→
yocxy2yocxy2

review

Analyze git diffs for SQL safety, concurrency, and LLM trust boundary violations.

Community
Advanced
TioSavichTioSavich

ship

Merge base branch, run tests, bump version, update changelog, commit, push, and create a pull request.

Community
Advanced
rsnormanrsnorman

quality-check

Run ESLint, Prettier, and TypeScript type checks on code.

Community
Intermediate
ajsai47ajsai47
11

review

Analyze git diffs for SQL injection, race conditions, and shell injection risks.

Community
Advanced