skills.rest
jonkiky
jonkikyCOMMUNITY
Explore all skills by this author →
GitHub

review

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

Updated Apr 2, 2026
Search Tags:#llm#sql#review#trust#diff#pr#code-review
One-click install
npx skills add https://github.com/jonkiky/ccdi-federation-ai --skill review-jonkiky
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/jonkiky/ccdi-federation-ai/tree/main/.agents/review
Command: npx skills add https://github.com/jonkiky/ccdi-federation-ai --skill review-jonkiky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR reviews are tedious and error-prone. This Skill analyzes diffs against the base branch to surface SQL safety issues, LLM trust boundary violations, conditional side effects, and other structural problems before merge.

Core Features & Use Cases

  • Detects SQL safety violations and unsafe diff patterns in pull requests
  • Checks for LLM trust boundary issues and potential side effects in diffs
  • Proactively suggests actions when a user is about to merge or land changes

Quick Start

Ask me to review a PR diff and I will check for SQL safety, LLM trust boundary violations, and conditional side effects.

Frequently Asked Questions about review

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

FAQPage Schema
How do I check a PR diff for SQL safety issues before merging?▼

To check a PR diff for SQL safety issues, analyze the changes against the base branch to detect unsafe patterns in SQL usage and data handling. This surfaces high-risk structural problems before you merge.

How do I detect LLM trust boundary violations in a pull request?▼

To detect LLM trust boundary violations in a pull request, analyze the code diff to assess trust boundary issues and potential conditional side effects. This identifies risks introduced by LLM interactions before merging.

What is the best way to automate code review for high-risk diff patterns?▼

Automating code review for high-risk diff patterns involves analyzing PR changes to locate unsafe SQL usage, LLM trust violations, and conditional side effects. This provides actionable recommendations and a concise risk summary to guide reviewers.

Can I get proactive recommendations when I am about to merge unsafe code changes?▼

Yes, you can get proactive recommendations when about to merge unsafe code changes. The system analyzes your diff against the base branch and suggests actions if it identifies high-risk patterns or trust boundary violations.

Does automated pre-landing PR review work without external dependencies?▼

Automated pre-landing PR review works without external dependencies. It directly analyzes your pull request diffs to locate SQL safety issues and LLM trust boundary violations, providing a concise risk summary without requiring additional components.

Related Skills

Explore More Software Engineering Skills→
rioX432rioX432
2

review

Review branch changes against the base branch for bugs, security, architecture, and quality issues.

Community
Advanced
xotongxotong

review

Analyze diffs against the base branch to report code quality and security issues.

Community
Advanced
nguyenphpnguyenphp
41

lint-and-validate

Run linters, type checkers, and security audits across Node.js and Python projects.

Community
Intermediate
mahg-esmahg-es
3

cicd-quality

Design and enforce CI/CD quality gates for code, tests, security, build, E2E, and performance.

Official
Advanced