review

Analyze git diffs for SQL safety risks and trust boundary violations.

Updated May 5, 2026

Search Tags:#git #static analysis #code review #security #pr review #sql safety

Ready to run

npx skills add https://github.com/iani-kuli/harness_bro --skill review-iani-kuli

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review
Source: https://github.com/iani-kuli/harness_bro/tree/main/.claude/skills/curated/gstack/review
Command: npx skills add https://github.com/iani-kuli/harness_bro --skill review-iani-kuli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, python, bun, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the pre-landing review process, identifying critical structural issues, SQL safety risks, and trust boundary violations before code is merged.

Core Features & Use Cases

Automated Safety Checks: Scans diffs for SQL injection, race conditions, and LLM trust boundary violations.
Proactive Guidance: Suggests improvements for code quality and structural integrity during the development lifecycle.
Use Case: Before landing a complex PR, use this Skill to ensure all new enum values are handled across the codebase and that no shell injection vulnerabilities were introduced.

Quick Start

Invoke the review skill to perform a comprehensive safety and structural check on your current git diff.

Frequently Asked Questions about review

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

FAQPage Schema

How do I automate SQL injection checks on a git diff before merging a pull request?▼

To automate SQL injection checks on a git diff before merging, use this Skill to analyze base branch changes and detect SQL safety risks, LLM trust boundary violations, and structural code issues during pre-landing reviews.

What is a pre-landing PR review for code quality and safety?▼

A pre-landing PR review for code quality and safety is an automated analysis of git diffs that proactively identifies structural integrity issues, race conditions, and trust boundary violations before code is merged into the base branch.

Do I need git and python installed to run automated static analysis on my pull requests?▼

Yes, you need git and python installed to run this static analysis, as the Skill requires git integration for diff comparison and python along with bun to execute its underlying review scripts.

How can I detect unhandled enum values and shell injection vulnerabilities in my code changes?▼

You can detect unhandled enum values and shell injection vulnerabilities by invoking this Skill to scan your current git diff, which proactively guides structural integrity and safety improvements across the codebase.

Can I use this to check LLM trust boundary violations in my codebase?▼

Yes, you can use this to check LLM trust boundary violations in your codebase, as the automated safety checks specifically scan git diffs to identify these risks alongside SQL injection and race conditions.