review

Analyze pull request diffs for SQL safety and trust boundary issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

An automated, structured pre-landing PR review that analyzes the current branch diffs against the base branch to identify SQL safety issues, potential LLM trust boundary violations, conditional side effects, and other structural risks. It provides clear guidance on what to fix before merging.

Core Features & Use Cases

  • Diff-based safety analysis: detects risky SQL patterns, data exposure risks, and structural issues in diffs.
  • Trust and boundary checks: flags LLM prompts, outputs, or tool usage that could leak sensitive data or violate trust boundaries.
  • Actionable guidance: supplies concrete recommendations and next steps to improve the quality and safety of changes before landing.

Quick Start

Instruct the Skill to perform a pre-landing PR review by analyzing the current branch diff against the base branch and reporting actionable findings.

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 on my pull request diff?

To perform a pre-landing code review, instruct the tool to analyze your current branch diff against the base branch. It identifies SQL safety issues, LLM trust boundary violations, and structural risks, then provides actionable fixes before merging.

What is diff-based safety analysis for pull requests?

Diff-based safety analysis detects risky SQL patterns, data exposure risks, and structural issues within pull request diffs. It proactively checks for conditional side effects and trust boundary violations before changes land in the base branch.

Can I check my diff for LLM trust boundary violations before merging?

Yes, you can check your diff for LLM trust boundary violations. The review process flags LLM prompts, outputs, or tool usage that could leak sensitive data, supplying concrete recommendations to secure trust boundaries before merging.

Does this code review tool detect SQL safety issues in branch diffs?

Yes, this code review tool detects SQL safety issues in branch diffs. It analyzes the current pull request diff against the base branch to identify risky SQL patterns and potential data exposure risks before code changes are merged.

What is the best way to identify conditional side effects in a PR?

The best way to identify conditional side effects in a PR is to use an automated diff analysis tool. It compares the current branch against the base branch to surface hidden structural risks and suggests proactive fixes before landing.

When do I need an automated pre-landing review for my code changes?

You need an automated pre-landing review when your code changes involve SQL queries, LLM tool usage, or complex logic with potential side effects. It performs a structured diff analysis to ensure safety and quality before merging.