review

Analyze pull request diffs for SQL safety, trust boundaries, and side effects.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/SeaLion-hub/DICEE --skill review-sealion-hub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/SeaLion-hub/DICEE/tree/main/.agents/skills/gstack/review
Command: npx skills add https://github.com/SeaLion-hub/DICEE --skill review-sealion-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps reviewers detect structural issues in PR diffs before merging by analyzing the diff against the base branch for SQL safety, LLM trust boundary violations, and side-effect risks, preventing risky changes from landing.

Core Features & Use Cases

  • Detect SQL safety issues like unsafe interpolations or missing parameterization in diffs.
  • Catch LLM trust boundary violations and potential prompt-injection risks in PR changes.
  • Identify conditional side effects and plan drift that could affect deployment or behavior.

Quick Start

Run the review workflow on a pull request to get an automated, structured assessment.

Frequently Asked Questions about review

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

FAQPage Schema
How do I detect SQL safety issues in a pull request diff?

Detect SQL safety issues in a pull request diff by analyzing branch changes against the base branch to identify unsafe interpolations and missing parameterization before merging.

Can I check for LLM trust boundary violations during code review?

Check for LLM trust boundary violations during code review by analyzing PR changes to catch potential prompt-injection risks and untrusted output handling before landing.

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

Identify conditional side effects in a PR by comparing the current branch against the base branch to detect plan drift and deployment risks within the diff.

How do I automate pre-landing PR review for safer diffs?

Automate pre-landing PR review for safer diffs by running a workflow that analyzes commits and structural changes to output a structured, actionable assessment.

Does static analysis of PR diffs require external dependencies?

Static analysis of PR diffs requires no external dependencies, operating directly on the branch comparison to evaluate SQL safety, LLM trust, and side-effect risks.