skills.rest
CaltexBevo
CaltexBevoCOMMUNITY
Explore all skills by this author →
GitHub

review

Analyze PR diffs for SQL safety, LLM trust boundaries, and change scope.

Updated Feb 5, 2026
Search Tags:#review#pull-request#diff-analysis#pr-checks#sql-safety#llm-trust
One-click install
npx skills add https://github.com/CaltexBevo/ihe-pulse --skill review-caltexbevo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/CaltexBevo/ihe-pulse/tree/main/.claude/skills/gstack.bak/review
Command: npx skills add https://github.com/CaltexBevo/ihe-pulse --skill review-caltexbevo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and guides pre-landing PR reviews by analyzing diffs against the base branch to catch SQL safety issues, LLM trust violations, and structural risks before merge.

Core Features & Use Cases

  • Diff-analysis for pre-landing PR reviews, focusing on SQL safety, LLM trust boundaries, conditional side effects, and change scope.
  • Proactive suggestions for potential merge risks and recommended next steps.
  • Use Case: When reviewing a PR that touches SQL, LLM prompts, or critical logic, run this to surface issues and suggestions before landing.

Quick Start

Run the review workflow on the current branch to start the pre-landing analysis.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate pre-landing PR review for SQL safety and LLM trust boundaries?▼

Pre-landing PR review automates diff analysis against a base branch to identify SQL safety issues, LLM trust boundary violations, and conditional side effects, emitting actionable risk guidance before merge.

What is diff analysis for catching merge risks in pull requests?▼

Diff analysis for pull requests loads branch changes against a base branch to surface structural risks and change scope drift, cross-checking the diff against planned scope to provide proactive merge recommendations.

How do I check a pull request diff for conditional side effects before merging?▼

Checking a pull request diff for conditional side effects involves analyzing the change scope across the diff to surface hidden structural risks and providing actionable next steps to ensure a clean merge.

Can I use automated PR checks to detect LLM trust violations in a diff?▼

Automated PR checks can detect LLM trust violations by analyzing the diff against the base branch during pre-landing review, evaluating prompt boundaries and structural risks to emit actionable guidance.

What is the best way to review SQL safety issues in a pull request diff?▼

The best way to review SQL safety issues in a pull request diff is running an automated pre-landing analysis that cross-checks changes against planned scope and surfaces risks for clean merges.

Does automated diff analysis work without external dependencies for pre-landing review?▼

Automated diff analysis works without external dependencies, loading the pull request diff against the base branch internally to evaluate SQL safety, LLM trust, and change scope for actionable recommendations.

Related Skills

Explore More Software Engineering Skills→
imonmiimonmi

review

Analyze pull request diffs for SQL safety and trust boundary issues.

Community
Advanced
chriswesttchriswestt

review

Analyze pull request diffs for SQL safety and trust boundary risks.

Community
Advanced
yanochka11yanochka11

review

Analyze repository diffs to identify defects, security risks, and structural problems.

Community
Advanced
anilveersingh1308anilveersingh1308

gstack-review

Review pull request diffs for SQL safety and trust-boundary violations.

Community
Advanced