skills.rest
cheng80
cheng80COMMUNITY
Explore all skills by this author →
GitHub

review

Identify SQL safety risks and LLM trust boundary violations in code diffs.

1|Updated Apr 12, 2026
Search Tags:#llm#safety#sql#review#diff#pull-request
One-click install
npx skills add https://github.com/cheng80/rummipoker --skill review-cheng80
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/cheng80/rummipoker/tree/main/.agents/skills/gstack-review
Command: npx skills add https://github.com/cheng80/rummipoker --skill review-cheng80

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR reviews that analyze diffs for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues before code merges.

Core Features & Use Cases

  • Pre-landing review for SQL safety checks, LLM alignment, and operational risk in diffs.
  • Automated checklists and suggested fixes for potential issues in PRs and code changes.
  • Use Case: When reviewing a PR that touches critical logic, run this skill to surface safety concerns and recommended actions.

Quick Start

Invoke this skill on a PR diff to surface SQL safety issues, LLM boundary concerns, and recommended fixes before merging.

Frequently Asked Questions about review

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

FAQPage Schema
How do I check a pull request diff for SQL safety risks before merging?▼

Pre-landing PR reviews analyze code diffs to surface SQL safety risks, LLM trust boundary violations, and conditional side effects. This automated check provides suggested fixes and records decisions for auditability before code merges into the base branch.

What are LLM trust boundary violations in code diffs?▼

LLM trust boundary violations occur when code changes improperly handle LLM alignment or operational boundaries. Pre-landing PR reviews identify these violations in pull request diffs, applying checks to prompt actionable fixes and record decisions for auditability.

Can I automate PR reviews to catch conditional side effects across a base branch?▼

Yes, automated pre-landing PR reviews trigger when merging changes or when reviewers request a review. They analyze code diffs across a base branch to catch conditional side effects, SQL safety risks, and LLM boundary violations, providing actionable fixes.

Does pre-landing code review work with standard pull request workflows?▼

Pre-landing code review integrates with standard pull request workflows by analyzing diffs across a base branch. It activates when reviewers request a review or when merging changes, applying checks for SQL safety and LLM alignment to provide actionable fixes.

What is the best way to surface operational risk in code changes before they land?▼

Running an automated pre-landing review on code diffs is the best way to surface operational risk. It identifies SQL safety issues, LLM trust boundary violations, and conditional side effects, generating an automated checklist with suggested fixes and recording decisions for auditability.

Why should I use an automated checklist for pull request safety checks?▼

Automated checklists for pull request safety checks consistently identify SQL safety risks, LLM boundary violations, and conditional side effects. They prompt actionable fixes for potential issues in code changes and record decisions for auditability before merging.

Related Skills

Explore More Software Engineering Skills→
ShmurdocShmurdoc

review

Analyze code diffs against the base branch to identify critical issues.

Community
Advanced
xotongxotong

review

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

Community
Advanced
iani-kuliiani-kuli

github-code-review

Analyzes git diffs and submits GitHub pull request reviews via CLI.

Community
Advanced
vnmoorthyvnmoorthy
2

review

Analyze diffs for SQL safety, trust boundary, and side-effect risks.

Community
Advanced