review

Analyze code diffs for SQL injection and trust boundary violations.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/sadie100/claude-dotfiles --skill review-sadie100
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/sadie100/claude-dotfiles/tree/main/skills/review
Command: npx skills add https://github.com/sadie100/claude-dotfiles --skill review-sadie100

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Read, Edit, Write, Grep, Glob, Agent, AskUserQuestion, WebSearch, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of code review, identifying potential issues like SQL safety, LLM trust boundary violations, and other structural problems before merging or landing code changes.

Core Features & Use Cases

  • Automated Code Review: Analyzes code diffs against the base branch for potential issues.
  • SQL Safety: Ensures SQL queries are safe and do not contain vulnerabilities.
  • LLM Trust Boundary Violations: Checks for potential violations of trust boundaries with large language models.
  • Use Case: When a developer wants to review a pull request or merge code changes, this Skill can be invoked to automatically check for common issues.

Quick Start

Use the review skill to review the code changes in the current pull request.

Frequently Asked Questions about review

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

FAQPage Schema
How can I automate code review for SQL injection vulnerabilities before merging changes?

Automated code review analyzes code diffs against the base branch to detect SQL injection vulnerabilities and structural issues before merging changes. It inspects SQL queries to ensure they do not contain exploitable safety flaws.

What are LLM trust boundary violations and how do I check for them in my code?

LLM trust boundary violations occur when untrusted data improperly crosses into large language model processing contexts. Automated code review checks code diffs to identify and flag these potential structural boundary violations during development.

Does automated code review work with my current pull request workflow?

Automated code review integrates into existing development workflows by analyzing code diffs against the base branch. It requires access to Bash, Read, Edit, Write, Grep, and Glob tools to inspect pull request changes.

How do I review code diffs for structural problems and security issues automatically?

To review code diffs automatically, the Skill uses Agent and WebSearch tools to analyze changes against the base branch. It identifies SQL safety issues, LLM trust boundary violations, and other structural problems.

What tools are required to run automated code review for SQL safety?

Running automated code review for SQL safety requires Bash, Read, Edit, Write, Grep, Glob, Agent, AskUserQuestion, and WebSearch tools to parse diffs, inspect code structures, and validate security boundaries.

Can code review identify issues beyond SQL injection in my pull requests?

Code review identifies issues beyond SQL injection by analyzing code diffs for LLM trust boundary violations and other structural problems. It ensures code quality and security are maintained before code changes land.