skills.rest
makyua-san
makyua-sanCOMMUNITY
Explore all skills by this author →
GitHub

review

Analyze code diffs for SQL safety and LLM trust boundary issues.

Updated Apr 5, 2026
Search Tags:#review#diff#code-quality#pull-request#risk-analysis#sql-safety#llm-trust
One-click install
npx skills add https://github.com/makyua-san/usecase-agent --skill review-makyua-san
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/makyua-san/usecase-agent/tree/main/.claude/skills/review
Command: npx skills add https://github.com/makyua-san/usecase-agent --skill review-makyua-san

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill analyzes diffs against the base branch for SQL safety, LLM trust boundary violations, and other structural issues, helping you catch defects before landing.

Core Features & Use Cases

  • Pre-landing PR review: checks for potential risk areas in code changes.
  • Diff-aware analysis: compares diffs to surface logical issues and side effects.
  • Proactive guidance: suggests improvements to improve code quality and safety.

Quick Start

Ask the reviewer to run the review workflow on the current branch to surface issues before merging.

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 issues before merging?▼

To check a pull request for SQL safety, run a diff-aware review against the base branch to identify structural issues and injection risks. This surfaces actionable recommendations to reduce risk before landing code changes.

What is an LLM trust boundary violation in code review?▼

An LLM trust boundary violation occurs when code changes improperly handle data boundaries between language models and external systems. Diff analysis identifies these potential security risks before merging pull requests.

How can I detect unintended side effects in a diff before landing?▼

To detect unintended side effects in a diff, compare code changes against the base branch to surface logical issues. This proactive analysis highlights risk areas and suggests improvements before merging.

Can I run an automated code quality review on my current branch?▼

Yes, you can run an automated code quality review on your current branch by analyzing the diff against the base branch. The workflow checks for SQL safety, LLM trust issues, and side effects to reduce risk before merging.

Does diff-aware risk analysis work for typical software projects?▼

Yes, diff-aware risk analysis works for typical software projects by comparing base branch diffs to surface logical issues and safety checks. It supports pre-landing pull request reviews across standard codebases.

Related Skills

Explore More Software Engineering Skills→
ByronWilliamsCPAByronWilliamsCPA
1

pr-prepare

Generate Markdown pull request descriptions from git context with conventional titles.

Official
Intermediate
u1pnsu1pns
8

code-reviewer

Identify security, quality, and performance risks in codebases before merge.

Community
Advanced
jm199seojm199seo

review

Analyze pull request diffs against the base branch for structural issues.

Community
Advanced
scanbottscanbott

review

Analyze PR diffs for SQL safety, LLM trust boundary, and side-effect issues.

Community
Advanced