skills.rest
scanbott
scanbottCOMMUNITY
Explore all skills by this author →
GitHub

review

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

Updated Apr 21, 2026
Search Tags:#review#diff#pr#risk-management#code-review#llm-trust
One-click install
npx skills add https://github.com/scanbott/claude-skills --skill review-scanbott
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/scanbott/claude-skills/tree/main/gstack/review
Command: npx skills add https://github.com/scanbott/claude-skills --skill review-scanbott

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review pull requests by analyzing the diff against the base branch to surface SQL safety issues, LLM trust boundary violations, conditional side effects, and other structural risks.

Core Features & Use Cases

  • Detect SQL safety concerns, data leakage risks, and unsafe shell usage in PR diffs.
  • Flag LLM trust boundary violations and potential prompt-injection vectors in code changes.
  • Provide prioritized, concrete fixes and recommendations for developers and reviewers during pre-landing reviews.

Quick Start

Analyze the current pull request diff to surface structured findings, severity, and actionable fixes.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a PR diff for SQL safety and LLM trust boundary violations?▼

PR diff review for SQL safety and LLM trust boundary violations analyzes changes against the base branch to detect unsafe queries, data leakage, and prompt-injection vectors. It outputs structured findings with severity levels and actionable fixes for developers.

What are common LLM trust boundary risks to look for in code review?▼

LLM trust boundary risks in code review include prompt-injection vectors and data leakage paths introduced in PR diffs. Analyzing these changes flags potential trust violations, providing prioritized and concrete fixes for reviewers during pre-landing workflows.

Can I detect conditional side effects and unsafe shell usage in a pull request diff?▼

Yes, analyzing a pull request diff can detect conditional side effects, unsafe shell usage, and SQL safety concerns. The review process surfaces these structural risks as structured findings with severity ratings and actionable recommendations.

Does pre-landing PR review work without additional dependencies or components?▼

Pre-landing PR review operates with no external dependencies or components, directly analyzing the diff to identify structural risks. It fits seamlessly into existing code-review workflows to provide severity-tagged findings and fixes.

What is the best way to automate risk management checks for pre-landing code review?▼

The best way to automate risk management for code review is analyzing PR diffs to surface SQL safety issues, LLM trust violations, and conditional side effects. This provides structured, severity-prioritized findings with concrete fixes directly in pre-landing workflows.

Related Skills

Explore More Software Engineering Skills→
AkbarDevopAkbarDevop

review

Identify production-risk findings in a code diff before merging.

Community
Advanced
ilamanovilamanov

fix-pr-reviews

Fetch and analyze GitHub PR review comments and markdown findings.

Community
Intermediate
aporto-techaporto-tech

gstack-review

Analyze code diffs for SQL safety and LLM trust boundary violations.

Official
Advanced
eliottbusinesseliottbusiness

requesting-code-review

Automate pre-commit code review with static analysis and security scanning.

Community
Advanced