review

Analyze diffs against the base branch for SQL safety and trust boundary issues.

Updated Mar 30, 2026

Search Tags:#routing #telemetry #code-review #pr-review #diff-analysis #sql-safety #llm-trust

Ready to run

npx skills add https://github.com/mulyoved/awesome-agent-ides --skill review-mulyoved

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/mulyoved/awesome-agent-ides/tree/main/.agents/skills/gstack/review
Command: npx skills add https://github.com/mulyoved/awesome-agent-ides --skill review-mulyoved

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates pre-landing PR review by analyzing diffs against the base branch to surface SQL safety issues, LLM trust boundary violations, conditional side effects, and other structural problems.

Core Features & Use Cases

Diff-based checks for SQL safety, data integrity, and race conditions in PR diffs.
Proactive guidance and routing suggestions to improve review quality and align with CLAUDE.md routing rules.
Telemetry-ready analytics to measure review outcomes and iteration speed.

Quick Start

Use this skill to review a PR by saying "review this PR" to trigger an automated diff analysis.

Frequently Asked Questions about review

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

FAQPage Schema

How do I automate pre-landing code review for SQL safety and race conditions?▼

Automated pre-landing code review analyzes PR diffs against the base branch to surface SQL safety issues, race conditions, and data integrity problems. It triggers when you request a PR review or diff check, providing proactive guidance without manual inspection.

What is an LLM trust boundary violation in a PR diff?▼

An LLM trust boundary violation occurs when untrusted input improperly crosses into trusted execution paths. Diff analysis identifies these structural issues during pre-landing review, flagging conditional side effects where LLM interactions bypass security constraints.

How do I check my diff for conditional side effects before merging?▼

To check your diff for conditional side effects, trigger an automated pre-landing review by asking to review your PR. The analysis compares changes against the base branch to detect unintended side effects, SQL safety risks, and LLM trust boundary violations.

Can I use diff analysis to review PRs with Bash, Grep, and WebSearch tools?▼

Diff analysis supports a broad toolset including Bash, Read, Edit, Write, Grep, Glob, Agent, AskUserQuestion, and WebSearch. You can review PRs by triggering the skill with commands like review this PR or check my diff.

What's the best way to review PR diffs for SQL safety and data integrity?▼

The best way to review PR diffs for SQL safety and data integrity is automated diff analysis against the base branch. It proactively surfaces race conditions and structural problems while providing routing suggestions aligned with your project rules.

Does automated PR review provide telemetry for measuring review outcomes?▼

Automated PR review provides telemetry-ready analytics to measure review outcomes and iteration speed. It analyzes diffs against the base branch and generates proactive guidance, enabling you to track the effectiveness of your pre-landing checks.