review

Analyzes diffs to detect SQL safety issues and LLM trust boundary violations before PR merge decisions are made.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Ulanxx/mzstack --skill review-ulanxx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Ulanxx/mzstack/tree/main/review
Command: npx skills add https://github.com/Ulanxx/mzstack --skill review-ulanxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR review often stalls when teams miss structural issues in code diffs. This Skill analyzes diffs against the base branch to surface SQL safety problems, LLM trust boundary violations, conditional side effects, and other structural concerns, enabling proactive quality checks before landing.

Core Features & Use Cases

  • Diff-scoped analysis for PR readiness, surfacing issues not caught by tests.
  • Proactive guidance for merges with a standardized AskUserQuestion workflow.
  • Plan-driven scope drift detection to ensure changes align with intent and TODOS.

Quick Start

Run the /review workflow on the current branch to generate actionable insights and suggested fixes.

Frequently Asked Questions about review

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

FAQPage Schema
How do I catch structural issues in code diffs before a PR merge?

To catch structural issues in code diffs before a PR merge, you can use automated diff analysis against the base branch to surface SQL safety problems, LLM trust boundary violations, and scope drift, enabling proactive quality checks.

How does scope drift detection work for pull requests?

Scope drift detection for pull requests works by analyzing diffs against plan-driven intent and TODOS. It checks whether code changes align with the original scope, ensuring that structural modifications do not deviate from the established goals before landing.

What is an LLM trust boundary validation in automated code review?

An LLM trust boundary validation in automated code review is a structural check that ensures language model interactions remain within defined safety limits. It analyzes diffs to detect violations where untrusted inputs or outputs cross secure boundaries in the application architecture.

Can I use automated AskUserQuestion workflows to guide merge decisions?

Yes, you can use standardized AskUserQuestion workflows to guide merge decisions. This approach integrates automated prompts into the diff analysis process, helping teams resolve structural issues and make informed decisions proactively before finalizing a pull request.

Does PR diff analysis require specific scripts or directory configurations?

PR diff analysis requires a YAML frontmatter with name and description, and optionally supports directories for scripts, references, and assets. It utilizes a toolset including Bash, Read, Edit, Write, Grep, Glob, Agent, and WebSearch to drive the workflow.