skills.rest
2300031147
2300031147COMMUNITY
Explore all skills by this author →
GitHub

review

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

Updated Apr 12, 2026
Search Tags:#quality#review#diff#static-analysis#pull-request#sql-safety#llm-trust
One-click install
npx skills add https://github.com/2300031147/clawopencode --skill review-2300031147
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/2300031147/clawopencode/tree/main/skills/review
Command: npx skills add https://github.com/2300031147/clawopencode --skill review-2300031147

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diff-based PR reviews are error-prone and slow. This Skill automates pre-landing checks by analyzing diffs for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues that commonly slip through manual reviews.

Core Features & Use Cases

  • Detects SQL safety and data integrity issues in changes before merge.
  • Flags LLM prompt/data-trust boundary violations and risky code paths.
  • Highlights conditional side effects and design concerns to accelerate reviewer decisions.
  • Integrates with automated review workflows to provide actionable remediation guidance.

Quick Start

Provide the current PR diff to the reviewer tooling to surface issues 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 automate code review for SQL safety and LLM trust boundary violations in a pull request?▼

Automated code review for SQL safety and LLM trust boundary violations analyzes PR diffs to detect risky code paths, data integrity issues, and structural concerns before merge, providing actionable remediation guidance to accelerate reviewer decisions.

What is a diff-based pre-landing review and how does it identify conditional side effects?▼

Diff-based pre-landing review examines pull request changes to identify conditional side effects by analyzing structural code modifications, flagging risky code paths and design concerns to ensure code safety and quality before changes are merged.

How do I run static analysis on a pull request diff to surface actionable risks?▼

Running static analysis on a pull request diff involves providing the current PR changes to automated review tooling, which surfaces actionable risks like SQL safety issues and LLM trust boundary violations, then suggests fixes for remediation.

Can I use automated review tooling to check SQL data integrity issues before merge?▼

Yes, automated review tooling checks SQL data integrity issues before merge by analyzing pull request diffs, detecting safety violations and risky code paths, and providing remediation guidance to ensure code quality.

Does pre-landing review integrate with model context protocol for automated checks?▼

Pre-landing review supports integration with the model context protocol, applying automated checks to pull request diffs to surface structural concerns, SQL safety issues, and LLM trust boundary violations with suggested fixes.

What are the limitations of automated pull request diff analysis for catching design concerns?▼

Automated pull request diff analysis focuses on structural concerns, SQL safety, and LLM trust boundaries, but may not capture complex architectural design issues, requiring human reviewers to evaluate broader contextual impact.

Related Skills

Explore More Software Engineering Skills→
yellow-seedyellow-seed

code-review

Identify and summarize differences between the current Git branch and its remote base branch.

Community
Basic
davpatel605-beepdavpatel605-beep

requesting-code-review

Run security scans, quality checks, and independent review workflows before git commits.

Community
Advanced
Kushal9889Kushal9889

husky

Sets up Husky git hooks to automate code quality checks and testing before commits.

Community
Intermediate
wangfeivwangfeiv

review

Analyze code diffs against mainline branches for SQL safety, concurrency, and trust boundaries.

Community
Intermediate