skills.rest
Jaykaijack
JaykaijackCOMMUNITY
Explore all skills by this author →
GitHub

review

Compare PR diffs against the base branch to identify SQL safety and trust boundary issues.

Updated Mar 15, 2026
Search Tags:#review#diff#code-quality#pull-request#sql-safety#llm-boundaries
One-click install
npx skills add https://github.com/Jaykaijack/openclaw-backup --skill review-jaykaijack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Jaykaijack/openclaw-backup/tree/main/skills/gstack/review
Command: npx skills add https://github.com/Jaykaijack/openclaw-backup --skill review-jaykaijack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR review workflow that analyzes diffs against the base branch for SQL safety, LLM trust boundaries, conditional side effects, and other structural issues. It helps you catch issues before merging and proactively suggests when changes are ready to land.

Core Features & Use Cases

  • Analyzes PR diffs for potential SQL safety issues and data integrity problems.
  • Checks LLM trust boundaries and guardrails in the proposed changes.
  • Evaluates conditional side effects and structural concerns to improve code quality.
  • Proactively suggests merge-ready changes when asked to review this PR or check diffs.

Quick Start

Submit the current PR branch to generate a diff against the base and trigger automated pre-landing checks.

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 for SQL safety risks before merging?▼

Pre-landing code review analyzes PR diffs against the base branch to identify SQL safety risks, LLM trust boundary issues, and structural problems. It applies deterministic checks and guardrails to proactively guide merge-readiness decisions before changes land.

What is the best way to review LLM trust boundaries in a code diff?▼

Reviewing LLM trust boundaries in a code diff is best handled by automated pre-landing checks that evaluate proposed changes for guardrails and structural concerns. This ensures trust boundaries are maintained before suggesting merge-ready changes.

How do I automate pre-landing code review for structural issues?▼

To automate pre-landing code review for structural issues, submit your current PR branch to generate a diff against the base. This triggers automated checks that evaluate conditional side effects and structural concerns to improve code quality.

Does pre-landing PR review work with conditional side effects and data integrity checks?▼

Pre-landing PR review works with conditional side effects and data integrity checks by analyzing the PR diff against the base branch. It integrates deterministic checks to identify structural problems and proactively suggest merge-ready changes.

When do I need to run a diff comparison against the base branch?▼

You need to run a diff comparison against the base branch when you want to perform a pre-landing PR review. This comparison evaluates SQL safety, LLM trust boundaries, and structural issues to determine if your changes are ready to merge.

Related Skills

Explore More Software Engineering Skills→
deveshkumarsdeveshkumars

review

Compare a branch diff against the base branch to detect scope drift and missing changes.

Community
Advanced
whd4whd4

review

Audit diffs for SQL safety, trust boundary violations, and side effects.

Community
Advanced
valegrajalesvalegrajales

land

Commit, push, and create a pull request with a handoff summary.

Community
Advanced
tsenseitsensei
3

review

Analyze diffs for SQL safety, LLM trust boundary violations, and structural risks.

Community
Advanced