skills.rest
himes19
himes19COMMUNITY
Explore all skills by this author →
GitHub

review

Review code diffs for SQL safety, race conditions, and LLM trust boundaries.

Updated Apr 12, 2026
Search Tags:#automation#git#sql#review#pr#llm-safety#race-condition
One-click install
npx skills add https://github.com/himes19/pulsevolt-infra --skill review-himes19
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/himes19/pulsevolt-infra/tree/main/skills/gstack/review
Command: npx skills add https://github.com/himes19/pulsevolt-infra --skill review-himes19

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR review. Analyzes diff for SQL safety, race conditions, LLM trust boundary violations, conditional side effects, and structural issues. Auto-fixes obvious issues, asks about complex ones. Use when reviewing code before merge, or when asked for "code review".

Core Features & Use Cases

  • Detects SQL safety issues, race conditions, LLM trust boundary violations, and unintended side effects in diffs.
  • Auto-fixes obvious issues and flags complex ones for human input during pre-merge reviews.
  • Scopes changes against requested intents and provides actionable remediation guidance.

Quick Start

Review a PR by following the steps to detect base branch, fetch the diff, and perform a two-pass review.

Frequently Asked Questions about review

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

FAQPage Schema
How do I catch race conditions and SQL safety issues before merging a PR?▼

Pre-landing PR reviews identify LLM trust boundary violations by analyzing your diff for unsafe trust boundaries. It flags complex LLM safety issues for human input and auto-fixes obvious ones.

What is the best way to automate code review for unintended side effects?▼

Automating code review for unintended side effects involves scoping diff changes against requested intents. This approach detects conditional side effects and structural issues, offering actionable remediation guidance during pre-merge reviews.

Can I auto-fix obvious bugs found during a pre-merge code review?▼

A two-pass code review systematically analyzes your diff in two stages to identify SQL safety issues and race conditions. It scopes changes against intent and provides actionable remediation guidance.

Does this pre-landing review work with standard git diffs?▼

Yes, this pre-landing review works with standard git diffs. The process detects the base branch, fetches the diff, and performs a two-pass review to identify structural issues and unintended side effects.

How do I perform a two-pass code review on a PR diff?▼

To perform a two-pass code review on a PR diff, you detect the base branch, fetch the diff, and execute the review. This structured process scopes changes against requested intents and flags complex issues for human input.

Related Skills

Explore More Software Engineering Skills→
kage1020kage1020

diff-report

Analyze branch changes and generate a five-section Markdown diff report.

Community
Intermediate
lachlanchenlachlanchen
1

prepare-pr

Rebase a GitHub pull request onto main, apply review fixes, run tests, and push.

Community
Advanced
Jamie-CuiJamie-Cui
28

finishing-a-development-branch

Finalize feature branches with pre-integration checks and merge strategy guidance.

Community
Intermediate
joyce820309joyce820309

review

Analyze code review diffs for SQL injection and trust boundary issues.

Community
Advanced