skills.rest
antriksh-29
antriksh-29COMMUNITY
Explore all skills by this author →
GitHub

review

Analyzes diffs for SQL safety, LLM trust boundary violations, and side effects pre-merge.

Updated Mar 24, 2026
Search Tags:#automation#llm#sql#review#diff#pull-request
One-click install
npx skills add https://github.com/antriksh-29/reddit-automation --skill review-antriksh-29
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/antriksh-29/reddit-automation/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/antriksh-29/reddit-automation --skill review-antriksh-29

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR review is automated to quickly identify SQL safety risks, LLM trust boundary violations, conditional side effects, and other structural issues in diffs before merging.

Core Features & Use Cases

  • Manual trigger only: invoke when a user types /review.
  • Analyzes diffs against the base branch to surface SQL safety concerns, LLM trust issues, and potential side effects.
  • Proactively suggests risk mitigation and improvement opportunities to reduce post-merge risk.

Quick Start

Type /review in the chat to trigger a pre-landing PR review.

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 for SQL safety and LLM trust boundaries?▼

Automated PR review analyzes code diffs against the base branch to detect SQL safety risks, LLM trust boundary violations, and structural side effects. Typing /review triggers the analysis and returns risk mitigation suggestions.

What is pre-landing pull request analysis and how does it handle code diffs?▼

Pre-landing pull request analysis evaluates code diffs before merging to identify structural risks and conditional side effects. It surfaces SQL safety concerns and LLM trust issues, returning actionable remediation steps to reduce post-merge risk.

Can I manually trigger automated diff analysis whenever I need it?▼

Automated diff analysis is strictly a manual trigger. Invoke the review process by typing /review in the chat whenever you have a pull request awaiting merge to scan for SQL and LLM structural issues.

Does PR review work with my existing pull request and diff workflow?▼

PR review applies directly to code changes in pull requests and diffs awaiting merge. It analyzes the diff against the base branch without requiring external dependencies or environment setup.

What are the limitations of automated diff review for catching side effects?▼

Automated diff review focuses specifically on SQL safety, LLM trust boundaries, and potential side effects. It proactively suggests risk mitigation but requires manual invocation and does not run automatically on every commit.

What's the best way to check for LLM trust boundary violations before merging?▼

Checking for LLM trust boundary violations is handled by automated pre-landing review. Typing /review analyzes your diff against the base branch to flag trust issues and suggest improvement opportunities before merge.

Related Skills

Explore More Software Engineering Skills→
andrewthetechieandrewthetechie
2

code-review

Review code changes against a base branch for maintainability and structural issues.

Community
Advanced
mdmagnuson-creatormdmagnuson-creator

merge-conflicts

Merge target branches into source branches and resolve pull request conflicts.

Community
Advanced
muratcankoylanmuratcankoylan
8

BACKPRESSURE

Create deterministic self-verification checks for AI coding agents.

Community
Intermediate
AndrewLi0420AndrewLi0420

review

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

Community
Advanced