skills.rest
jkhowland
jkhowlandCOMMUNITY
Explore all skills by this author →
Website𝕏@jkhowlandGitHub

review

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

Updated Mar 11, 2026
Search Tags:#automation#code-quality#pr-review#diff-analysis#sql-safety#llm-boundary#prelanding
One-click install
npx skills add https://github.com/jkhowland/jkhowland --skill review-jkhowland
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/jkhowland/jkhowland/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/jkhowland/jkhowland --skill review-jkhowland

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR review tool that analyzes diffs against the base branch to detect SQL safety issues, LLM trust boundary violations, conditional side effects, and other structural risks before merging.

Core Features & Use Cases

  • Diff-based safety analysis for PRs to prevent risky merges
  • Checks for SQL safety, LLM boundary compliance, and structural integrity
  • Proactive guidance and remediation suggestions when changes are about to land

Quick Start

Provide the PR diff or branch URL and I will run the review to surface actionable findings.

Frequently Asked Questions about review

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

FAQPage Schema
How do I analyze code diffs for SQL safety and LLM trust boundary issues before merging?▼

You provide the PR diff or branch URL, and the tool runs a diff-based safety analysis against the base branch. It identifies SQL safety issues, LLM boundary violations, and structural risks, then prompts for human input on complex decisions during the review.

What is pre-landing code review and when do I need it?▼

Pre-landing code review is the process of analyzing pull request diffs to catch structural risks and safety issues before changes are merged into the base branch. You need it to proactively enforce safe defaults and prevent risky code from landing in your repository.

Can I use automated diff analysis to check for conditional side effects in pull requests?▼

Yes, automated diff analysis can check for conditional side effects across repository branches. It evaluates pull request changes, flags structural risks, and provides remediation suggestions to ensure code quality and safety before landing.

Does pre-landing PR review work with my existing repository branches?▼

Pre-landing PR review works across repository branches by analyzing the diff against the base branch. You simply provide the PR diff or branch URL, and it surfaces actionable findings regarding SQL safety, LLM boundaries, and structural integrity without requiring additional dependencies.

What are the limitations of automated diff analysis for preventing risky merges?▼

Automated diff analysis focuses on SQL safety, LLM trust boundaries, and conditional side effects, but it prompts for human input on complex decisions during review. It enforces safe defaults and provides remediation guidance, yet cannot fully replace manual oversight for nuanced architectural changes.

Related Skills

Explore More Software Engineering Skills→
justifi-techjustifi-tech
5

pr-review

Automate GitHub PR reviews with size checks and gh pr review actions.

Official
Advanced
ligianehualigianehua

review

Analyze git diffs for SQL safety, LLM trust boundaries, and structural defects.

Community
Advanced
yanochka11yanochka11

review

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

Community
Advanced
diiviikk5diiviikk5

review

Analyze PR diffs for SQL safety, LLM trust boundaries, and structural issues.

Community
Advanced