skills.rest
Analog-Labs
Analog-LabsOFFICIAL
Explore all skills by this author →
Website𝕏@OneAnalogGitHub

review

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

Updated Feb 28, 2026
Search Tags:#review#diff#code-quality#pr#sql-safety#llm-trust
One-click install
npx skills add https://github.com/Analog-Labs/pixelport-launchpad --skill review-analog-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Analog-Labs/pixelport-launchpad/tree/main/.agents/skills/gstack/review
Command: npx skills add https://github.com/Analog-Labs/pixelport-launchpad --skill review-analog-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes diffs against the base branch to surface SQL safety issues, data integrity concerns, and LLM prompt boundary risks before merging.

Core Features & Use Cases

  • Diff analysis for SQL safety, LLM trust boundaries, and conditional side effects.
  • Generates actionable guidance and prompts for governance reviews.
  • Use cases include pre-landing PR reviews, code-quality checks, and merge readiness.

Quick Start

Review the current PR diff to identify high-risk areas 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 check pull request diffs for SQL safety issues before merging?▼

To check pull request diffs for SQL safety issues, analyze the current PR against the base branch to surface data integrity risks. This process proactively generates actionable fixes and guidance for governance reviews before code lands.

What is an LLM trust boundary violation in code review?▼

An LLM trust boundary violation occurs when prompt boundaries are breached within application logic. PR review analyzes your diff to detect these LLM prompt boundary risks, ensuring structured findings and suggested fixes before merge.

How do I review code for conditional side effects and merge readiness?▼

To review code for conditional side effects and merge readiness, analyze the pull request diff against the base branch. This surfaces SQL safety issues, LLM trust boundary violations, and side effects with actionable guidance for reviewers.

Does automated PR review work for catching LLM prompt boundary risks?▼

Yes, automated PR review works for catching LLM prompt boundary risks by analyzing diffs against the base branch. It identifies conditional side effects and generates structured findings with escalation guidelines for reviewers.

What's the best way to enforce code quality and governance during pre-landing reviews?▼

The best way to enforce code quality and governance during pre-landing reviews is to analyze PR diffs for SQL safety, LLM trust boundaries, and side effects. This generates actionable guidance, suggested fixes, and prompts for governance reviews.

Related Skills

Explore More Software Engineering Skills→
ruskibeatsruskibeats

review

Review code diffs against coding standards and specifications.

Community
Advanced
kunalrawat425kunalrawat425

review

Analyze diffs against the base branch for SQL safety, trust boundary, and side-effect issues.

Community
Advanced
shihwesleyshihwesley

review

Analyze branch diffs for SQL safety and trust boundary issues.

Community
Advanced
AlphaLab-USTCAlphaLab-USTC
131

requesting-code-review

Request code reviews for git commit ranges before merge.

Community
Intermediate