skills.rest
agatx
agatxCOMMUNITY
Explore all skills by this author →
GitHub

review

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

5|2|Updated Dec 27, 2025
Search Tags:#security#llm#review#trust#diff#pr#code-review
One-click install
npx skills add https://github.com/agatx/serenada --skill review-agatx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/agatx/serenada/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/agatx/serenada --skill review-agatx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes diffs against the base branch to surface SQL safety issues, LLM trust boundary violations, and other structural problems in PRs. It helps teams catch risky changes before merging by highlighting potential vulnerabilities, misconfigurations, and behavior changes.

Core Features & Use Cases

  • Diff analysis against the base branch to surface SQL safety risks, LLM trust boundary violations, and structural issues.
  • Proactive suggestions for safe merging, including mitigation steps and best practices for PR reviews.
  • Use cases include pre-landing PR reviews, code review workflows, and diff-checks when preparing for merges.

Quick Start

Tell me to review a PR or diff against the base branch and I will analyze it for safety, trust, and structural issues.

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?▼

Analyze your PR diff against the base branch to surface SQL safety issues and LLM trust boundary violations. This review process highlights potential vulnerabilities, misconfigurations, and behavior changes to catch risky code before merging.

What is pre-landing code review for merge safety?▼

Pre-landing code review is the process of analyzing diffs against a base branch to identify structural problems and risky changes before merging. It provides proactive suggestions and clear action items to improve merge safety and trust.

How do I check a diff for security vulnerabilities before merging?▼

Check your diff by analyzing it against the base branch to surface security vulnerabilities, misconfigurations, and behavior changes. This diff check provides proactive suggestions and mitigation steps to ensure safe merging.

Can I use automated PR reviews to catch structural problems in my code?▼

Yes, you can trigger automated checks and human review guidance by analyzing PR diffs. The review surfaces structural problems, SQL safety issues, and LLM trust boundary violations, providing clear action items for safe merges.

What are common LLM trust boundary issues found in PR reviews?▼

LLM trust boundary violations are risky changes in your diff that compromise the safety or integrity of language model integrations. Analyzing your PR against the base branch surfaces these structural issues alongside SQL safety risks before merging.

When do I need a diff check for merge safety and trust?▼

You need a diff check when preparing for merges and conducting code review workflows. It analyzes changes against the base branch to proactively surface SQL safety issues, trust boundary violations, and structural problems before landing code.

Related Skills

Explore More Software Engineering Skills→
jm199seojm199seo

review

Analyze pull request diffs against the base branch for structural issues.

Community
Advanced
MFS-codeMFS-code
8

review

Review git diffs for SQL, LLM trust, and concurrency risks.

Community
Advanced
TimHL5TimHL5

review

Analyze pull request diffs for SQL safety and data integrity risks.

Community
Advanced
ToanPV90ToanPV90

sast-scanning

Detects source code vulnerabilities via static analysis with JSON/SARIF outputs.

Community
Advanced