skills.rest
agwacom
agwacomOFFICIAL
Explore all skills by this author →
GitHub

review

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

Updated Mar 30, 2026
Search Tags:#llm#sql#review#trust#diff#pr
One-click install
npx skills add https://github.com/agwacom/adeel --skill review-agwacom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/agwacom/adeel/tree/main/skills/review
Command: npx skills add https://github.com/agwacom/adeel --skill review-agwacom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

An automated Skill that helps engineering teams quickly identify and explain issues in pull request diffs, including potential SQL safety concerns, LLM trust boundary violations, and risky code patterns, before merging.

Core Features & Use Cases

  • Automated pre-landing PR reviews that analyze diffs for structural risks, data-safety checks, and policy adherence.
  • Guidance for reviewers with concrete next steps, suggested reforms, and escalation prompts.
  • Supports decision-making for merge readiness by highlighting high-risk changes and recommended mitigations.

Quick Start

Run the /adeel:review command on a PR to trigger an automated pre-landing review.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate PR diff reviews for SQL safety and LLM trust boundaries?▼

To automate PR diff reviews, run the /adeel:review command on a pull request. It analyzes base-branch diffs and PR descriptions to detect SQL safety issues, LLM trust boundary violations, and risky code patterns before merging.

What are LLM trust boundary violations in pull request diffs?▼

LLM trust boundary violations in pull request diffs occur when untrusted model outputs bypass security controls. The review process identifies these structural risks alongside data-safety checks to ensure changes align with project goals.

How do I check merge readiness for pull requests with risky code patterns?▼

To check merge readiness for pull requests, trigger an automated pre-landing review. It highlights high-risk changes, conditional side effects, and policy adherence, delivering structured guidance with concrete next steps and recommended mitigations.

Can I use automated code reviews to detect conditional side effects in base-branch diffs?▼

Yes, you can use automated code reviews to detect conditional side effects in base-branch diffs. The review applies to PR descriptions and diffs, identifying risky code patterns and providing actionable guidance for developers and reviewers.

What is the best way to provide actionable guidance for reviewers on SQL safety issues?▼

The best way to provide actionable guidance for reviewers is to run automated pre-landing PR reviews. This approach detects SQL safety concerns, explains issues in the diffs, and supplies suggested reforms and escalation prompts.

When should I not use automated PR diff analysis?▼

You should not rely on automated PR diff analysis when a pull request lacks a base-branch diff or PR description. The analysis requires these inputs to evaluate SQL safety, LLM trust boundaries, and alignment with project goals.

Related Skills

Explore More Software Engineering Skills→
JonnyCBBJonnyCBB

pr-description

Generate structured PR descriptions from git diffs for GitHub flows.

Community
Advanced
remiboivin021remiboivin021

release

Evaluate feature branches against acceptance criteria and output a MERGE READY or NOT READY verdict.

Community
Advanced
evanfang0054evanfang0054

requesting-code-review

Automate code review requests with detailed context for reviewers.

Community
Advanced
seb1nseb1n
147

static-application-security-testing

Run SAST scans with Semgrep and CodeQL to detect vulnerabilities in source code.

Community
Advanced