skills.rest
mmunro3318
mmunro3318COMMUNITY
Explore all skills by this author →
GitHub

review

Compare code diffs against the main branch to identify SQL safety issues, LLM trust risks, and conditional side effects.

Updated Aug 27, 2026
Search Tags:#automation#llm#sql#review#trust#diff#pull-request
One-click install
npx skills add https://github.com/mmunro3318/3d-render-pipeline --skill review-mmunro3318
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/mmunro3318/3d-render-pipeline/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/mmunro3318/3d-render-pipeline --skill review-mmunro3318

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when asked to "review this PR", "code review", "pre-landing review", or "check my diff". Proactively suggest when the user is about to merge or land code changes.

Core Features & Use Cases

  • Surface critical findings in diffs comparing to base branches, including SQL safety checks, LLM trust boundary considerations, and stability concerns.
  • Provide structured feedback with actionable fixes, including auto-fixed items where possible.
  • Integrate with gstack-style workflows to guide decision-making during PR reviews.

Quick Start

Run this skill on your PR branch to generate a structured PR review report.

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 code review for SQL safety issues in pull requests?▼

Automated pre-landing code review identifies SQL safety issues by comparing pull request diffs against the base branch. It generates a structured report with actionable fixes and optional design review notes.

What are common LLM trust boundary violations and how can I detect them before merging?▼

Detecting LLM trust boundary violations before merging involves analyzing code diffs for risks associated with LLM outputs. Pre-landing review compares changes against the main branch to surface these critical findings.

How do I check my diff for conditional side effects before landing code changes?▼

Checking your diff for conditional side effects requires comparing your branch against the main branch. Pre-landing review applies a predefined checklist to surface stability concerns and suggest fixes.

Can I generate structured PR review reports with actionable items automatically?▼

Generating structured PR review reports with actionable items is possible by running automated checks on your pull request. The review process applies a checklist to surface critical findings and suggest auto-fixed items.

Does automated pre-landing review work without additional dependencies?▼

Automated pre-landing review operates without additional dependencies. It analyzes diffs against base branches and applies a predefined review checklist to produce structured feedback.

When should I use an automated pull request review checklist?▼

An automated pull request review checklist should be used when you are about to merge or land code changes. It proactively checks diffs for SQL safety, LLM trust risks, and structural side effects.

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
s3nex-coms3nex-com

pr-merge-orchestrator

Coordinate pull request lifecycle from review through merge with mandatory gates.

Community
Advanced
s977043s977043
2

code-review

Analyze pull-request diffs to identify security, performance, quality, and test risks.

Community
Basic
ScivorScivor

review

Analyze diffs for SQL safety, LLM trust boundaries, and conditional side effects.

Community
Advanced