review

Analyze PR diffs for SQL safety and trust boundary violations.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/abhishekmmgn/didactic-invention --skill review-abhishekmmgn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/abhishekmmgn/didactic-invention/tree/main/.agents/skills/gstack/review
Command: npx skills add https://github.com/abhishekmmgn/didactic-invention --skill review-abhishekmmgn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diff analysis for pre-landing PR reviews to detect SQL safety issues, LLM trust boundary violations, conditional side effects, and structural risks before merging.

Core Features & Use Cases

  • Analyzes diffs against the base branch for SQL safety, LLM trust boundary violations, and other structural issues.
  • Guides gating and decision-making with plan-mode rules, AskUserQuestion prompts, and proactive checks.
  • Supports safe plan-mode operations, telemetry prompts, and routing guidance to improve code quality.

Quick Start

Invoke the skill on a PR diff to automatically analyze changes and generate a decision brief with recommended actions.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate code review for SQL safety in pull requests?

Automated PR review catches SQL safety issues by analyzing diffs against the base branch to detect unsafe modifications. It evaluates patch sets to identify structural risks and SQL injection vectors before merge.

What is an LLM trust boundary violation in diff analysis?

An LLM trust boundary violation in diff analysis occurs when code changes allow untrusted inputs to cross into LLM processing without proper safety rails. This Skill detects such violations by analyzing PR diffs before merge.

How do I check a pull request diff for conditional side effects before merging?

You can check a pull request diff for conditional side effects by applying automated diff analysis against the base branch. This process identifies hidden structural issues and side effects to generate a decision brief with recommended actions.

Can I use automated diff analysis to gate pull request merges?

Yes, you can use automated diff analysis to gate pull request merges. The process supports gating decisions through plan-mode rules, AskUserQuestion prompts, and proactive checks to enforce safety rails before code lands.

Does automated code review work with patch sets and spawned sessions?

Automated code review works with patch sets and spawned sessions by applying diff analysis with safety rails and monitoring. It supports plan-mode operations and routing guidance to evaluate code changes across active sessions.

What are the limitations of automated diff analysis for pre-landing code reviews?

The limitations of automated diff analysis for pre-landing code reviews include its focus on structural risks, SQL safety, and LLM trust boundaries. It operates within plan-mode safety rails and may require AskUserQuestion prompts for complex gating decisions.