skills.rest
martin-hsu-test
martin-hsu-testCOMMUNITY
Explore all skills by this author →
GitHub

review

Identify SQL safety and trust boundary risks in branch diffs before merging.

1|Updated Apr 8, 2026
Search Tags:#safety#quality#governance#review#code-review#pull-request#diff-analysis
One-click install
npx skills add https://github.com/martin-hsu-test/gstack-gemini-slim --skill review-martin-hsu-test
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/martin-hsu-test/gstack-gemini-slim/tree/main/.gemini/skills/gstack-review
Command: npx skills add https://github.com/martin-hsu-test/gstack-gemini-slim --skill review-martin-hsu-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes the diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use before merging to prevent risky changes from going live.

Core Features & Use Cases

  • Diff-based pre-landing PR review for safety, trust, and governance issues.
  • Proactively suggests merge-readiness improvements and highlights risk areas.
  • Produces a concise review narrative to guide teammates during code review.

Quick Start

Review the current branch against the base to pre-validate changes before merge.

Frequently Asked Questions about review

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

FAQPage Schema
How do I check a pull request for SQL safety and trust boundary violations before merging?▼

To check a pull request for SQL safety and LLM trust boundary violations, review the diff against the base branch before merging. This pre-landing review surfaces structural issues and conditional side effects to enforce governance.

What is diff analysis for pre-landing code review?▼

Diff analysis for pre-landing code review identifies risks between the current branch and base branch. It proactively surfaces merge-readiness issues, highlighting risk areas and providing actionable review guidance within the git workflow.

How do I generate a code review narrative from a branch diff?▼

Generate a code review narrative from a branch diff by analyzing changes against the base branch. This produces actionable review guidance for teammates, highlighting structural risks and merge-readiness improvements before code lands.

Can I use automated diff analysis to catch conditional side effects in my base branch?▼

Yes, you can use automated diff analysis to catch conditional side effects by comparing your current branch with the base branch. This pre-landing review surfaces structural issues to prevent risky changes from going live.

What are the limitations of relying on diff analysis for code governance?▼

A limitation of diff-based code governance is that it only analyzes changes between the current and base branch. While it surfaces LLM trust boundary violations and SQL safety concerns, it may miss broader architectural issues outside the diff scope.

Related Skills

Explore More Software Engineering Skills→
timurgaleevtimurgaleev
5

review

Diagnose PR diffs for SQL safety and LLM trust boundary issues.

Community
Advanced
segersnielssegersniels

Actionable Comments

Transform review findings into actionable pull request comments.

Community
Intermediate
MFS-codeMFS-code
8

review

Review git diffs for SQL, LLM trust, and concurrency risks.

Community
Advanced
jm199seojm199seo

review

Analyze pull request diffs against the base branch for structural issues.

Community
Advanced