review

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

10|3|Updated Mar 25, 2026

Search Tags:#review #code-quality #pull-request #diff-analysis #SQL-safety #LLM-trust

Ready to run

npx skills add https://github.com/olaafrossi/FoamPilot --skill review-olaafrossi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/olaafrossi/FoamPilot/tree/main/.claude/skills/review
Command: npx skills add https://github.com/olaafrossi/FoamPilot --skill review-olaafrossi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR reviews are often lengthy and error-prone. This Skill analyzes diffs against the base branch to surface SQL safety issues, LLM trust boundary violations, conditional side effects, and other structural problems before merging.

Core Features & Use Cases

Analyzes diffs for SQL safety concerns, including potential injection risks and unsafe query patterns.
Detects LLM trust boundary issues and potential data leakage in code changes.
Flags conditional side effects, architectural drift, and unintended edits across commits.
Provides concrete remediation guidance and merge-readiness signals for code changes.

Quick Start

After activating, provide the PR diff or link to the PR; the Skill will return a structured review with findings and recommended next steps.

Frequently Asked Questions about review

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

FAQPage Schema

How do I automate pull request reviews for SQL safety and data leakage?▼

Automated PR review analyzes your diffs against the base branch to surface SQL injection risks, LLM trust boundary violations, and conditional side effects. It provides structured findings and remediation guidance to ensure merge readiness.

How does diff analysis detect LLM trust boundary violations in code changes?▼

Diff analysis detects LLM trust boundary violations by comparing code changes against the base branch to identify potential data leakage and unsafe data handling patterns. It flags these risks before merging to prevent unintended exposure.

Can I use automated code review to flag conditional side effects before merging?▼

Yes, automated code review flags conditional side effects, architectural drift, and unintended edits across commits by analyzing the PR diff. This proactive quality signal helps prevent operational integrity issues during merges.

What is the best way to audit pull request diffs for unsafe query patterns?▼

Auditing PR diffs for unsafe query patterns is best handled by an automated review assistant that analyzes changes against the base branch. It identifies potential SQL injection risks and provides concrete remediation commands.

Do I need to provide the full repository to get merge readiness signals from a PR review?▼

No, you do not need to provide the full repository to get merge readiness signals. You simply provide the PR diff or a link to the PR, and the review assistant will return structured findings and recommended next steps.