skills.rest
aimasteracc
aimasteraccCOMMUNITY
Explore all skills by this author →
GitHub

review

Analyze branch diffs for SQL safety, trust boundaries, and side effects.

46|13|Updated Jul 30, 2025
Search Tags:#git#code-quality#pr-review#diff-analysis#sql-safety#llm-trust#pre-landing
One-click install
npx skills add https://github.com/aimasteracc/tree-sitter-analyzer --skill review-aimasteracc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/aimasteracc/tree-sitter-analyzer/tree/main/.claude/skills/review
Command: npx skills add https://github.com/aimasteracc/tree-sitter-analyzer --skill review-aimasteracc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR reviews often require manually inspecting diffs against a base branch to catch structural issues, unsafe changes, and misalignments with project policies. This Skill automates that pre-landing review workflow, surfacing risk indicators before a merge.

Core Features & Use Cases

  • Analyze the current branch diff against the base to surface potential issues (SQL safety, LLM trust boundaries, and structural risk).
  • Proactively suggest merge-safety recommendations when you prepare to land changes.
  • Integrate with standard PR workflows to reduce manual review time and improve quality.

Quick Start

Run the review skill to analyze the current branch's diff against the base branch and surface structural issues.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate PR review and diff analysis before merging?▼

Automate PR review by analyzing the current branch diff against the base branch to surface structural issues, SQL safety risks, and LLM trust boundary violations. This provides actionable findings and recommendations to guide pre-landing reviews and reduce manual inspection time.

Can I check SQL safety in my git diff before landing changes?▼

Yes, you can check SQL safety in your git diff by running an automated pre-landing review. It analyzes the current branch diff to detect unsafe SQL changes and structural risks, providing recommendations to ensure merge safety before you land changes.

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

An LLM trust boundary violation in code review occurs when changes improperly cross security or trust limits in LLM interactions. Automated diff analysis detects these violations by checking the current branch against the base branch to surface risk indicators before a merge.

Does the automated diff analysis work with conditional side effects?▼

Yes, automated diff analysis works with conditional side effects by checking the current branch diff against the base branch. It surfaces these structural issues during the pre-landing review to provide actionable findings and merge-safety recommendations.

What are the limitations of automated pre-landing code review?▼

Automated pre-landing code review focuses on structural issues, SQL safety, LLM trust boundaries, and conditional side effects. It requires a current branch diff against a base branch to surface risk indicators, meaning it supplements but does not replace manual PR workflows.

Related Skills

Explore More Software Engineering Skills→
imonmiimonmi

review

Analyze pull request diffs for SQL safety and trust boundary issues.

Community
Advanced
alpe89alpe89

code-reviewer

Analyzes pull request diffs for complexity, risk, and quality issues across multi-language repositories.

Community
Intermediate
anhhung04anhhung04
1

github-triage

Automate task creation and status updates from GitHub issues via the API.

Community
Basic
balajivisbalajivis
2

review

Analyze Git-based code diffs to detect structural risks before merging.

Community
Advanced