skills.rest
JeremiahEllington
JeremiahEllingtonCOMMUNITY
Explore all skills by this author →
GitHub

review

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

Updated Apr 6, 2026
Search Tags:#security#review#diff#PR#code-review#risk-analysis
One-click install
npx skills add https://github.com/JeremiahEllington/NoahEllington --skill review-jeremiahellington
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/JeremiahEllington/NoahEllington/tree/main/.claude/skills/review
Command: npx skills add https://github.com/JeremiahEllington/NoahEllington --skill review-jeremiahellington

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

  • Automated diff analysis for SQL safety and trust boundaries.
  • Detection of conditional side effects and potential integration risks.
  • Proactive risk signaling for pre-landing PR reviews across codebases and data changes.

Quick Start

Provide the PR diff or URL and ask Claude to review it against the base branch.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate code review for SQL safety risks in a PR diff?▼

Automated code review analyzes PR diffs against the base branch to surface SQL safety issues, LLM trust boundary violations, and conditional side effects before merging. Provide the PR diff or URL to get actionable guidance on fixing identified structural problems.

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

LLM trust boundary violation detection is an automated diff analysis that identifies structural risks where untrusted inputs cross LLM integration boundaries. It surfaces these issues during pre-landing PR reviews so you can fix trust boundary gaps before merging.

Can I use automated risk analysis to check conditional side effects before merging?▼

Yes, automated risk analysis detects conditional side effects and potential integration risks by analyzing diffs against the base branch. It checks the diff with your standard tooling and outputs actionable guidance to fix identified structural issues before merging.

How do I review a PR diff against the base branch for structural issues?▼

To review a PR diff against the base branch, provide the diff or URL and run automated risk analysis. The review checks for SQL safety, LLM trust boundary violations, and conditional side effects, outputting actionable guidance to fix identified structural problems.

Does automated PR review work without specific dependencies or components?▼

Yes, automated PR review works without specific dependencies or components. It analyzes the diff you provide against the base branch using your standard tooling to surface SQL safety, trust boundary, and conditional side effect risks before merging.

What's the best way to surface integration risks in pre-landing code reviews?▼

The best way to surface integration risks in pre-landing code reviews is automated diff analysis against the base branch. It proactively signals SQL safety issues, LLM trust boundary violations, and conditional side effects across codebases and data changes before merging.

Related Skills

Explore More Software Engineering Skills→
shopsysshopsys
349

pr-diff-fetcher

Fetch pull request diffs, metadata, and commit messages via GitHub CLI or API.

Official
Advanced
zz8011zz8011

review

Analyze PR diffs for SQL safety, LLM trust boundary violations, and conditional side effects.

Community
Intermediate
mattothomasmattothomas

review

Analyze PR diffs for SQL safety, LLM trust boundary violations, and side-effect risks.

Community
Intermediate
nerdsanenerdsane
46

desloppify

Scan codebases for quality issues and technical debt across 28 languages.

Community
Advanced