skills.rest
kadenn
kadennCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

review

Analyze PR diffs for SQL safety and LLM boundary violations.

Updated Aug 23, 2026
Search Tags:#automation#quality-assurance#code-review#pr-review#diff-analysis#sql-safety#llm-trust
One-click install
npx skills add https://github.com/kadenn/kstack --skill review-kadenn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/kadenn/kstack/tree/main/review
Command: npx skills add https://github.com/kadenn/kstack --skill review-kadenn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR review identifies and reports issues in a pull request by analyzing the diff against the main branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues that could cause bugs or risk release quality.

Core Features & Use Cases

  • Diff-based checks for SQL safety and data integrity, ensuring changes won't introduce unsafe queries or data mutations.
  • LLM trust boundary verification to prevent prompt-related leakage or unsafe outputs in code changes.
  • Stepwise, reproducible checkout and review workflow that highlights actionable issues and preserves reviewer intent for governance.

Quick Start

Instruct the system to run the /review workflow against your feature/PR branch to generate findings and recommended fixes.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate PR review to catch SQL safety issues before merging?▼

Pre-landing PR review analyzes branch diffs against the main branch to detect unsafe SQL queries and data mutations before merging. It applies a two-pass checklist approach to identify structural problems and generate remediation steps for safe releases.

What is an LLM trust boundary violation in code changes?▼

An LLM trust boundary violation occurs when code changes introduce risks of prompt-related leakage or unsafe LLM outputs. Pre-landing PR review verifies these boundaries during diff analysis to prevent security and integrity issues in your releases.

Can I run pre-landing code review on configuration and documentation changes?▼

Yes, pre-landing code review applies to repository changes including code, configuration, and documentation. It analyzes the full diff to ensure structural problems and conditional side effects are caught across all file types for maintainable releases.

What's the best way to identify conditional side effects in a pull request diff?▼

Analyzing the PR diff against the main branch is the best way to identify conditional side effects. This pre-landing review process highlights actionable issues and provides recommended fixes using a reproducible checkout workflow.

Does automated diff analysis require a specific testing framework to check release quality?▼

No specific testing framework is required. Automated diff analysis independently reviews SQL safety, LLM boundaries, and structural issues by applying a reproducible stepwise workflow and checklist to your feature branch.

Related Skills

Explore More Software Engineering Skills→
mhawthornemhawthorne
11

gza-code-review-interactive

Review committed changes on a feature branch against main.

Community
Advanced
curielmccurielmc

review

Analyze PR diffs for SQL safety, LLM trust, and structural issues.

Community
Advanced
tygwantygwan
1

quality-gate

Automate quality validation at pre-commit, pre-merge, pre-release, and post-release CI gates.

Community
Advanced
mymx2mymx2
4

sql-parser-cst

Parse SQL statements into a Concrete Syntax Tree preserving comments and whitespace.

Community
Advanced