review

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

Updated Oct 15, 2025
One-click install
npx skills add https://github.com/vibrationalforce/Echoelmusic --skill review-vibrationalforce
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/vibrationalforce/Echoelmusic/tree/main/.claude/skills/gstack/review
Command: npx skills add https://github.com/vibrationalforce/Echoelmusic --skill review-vibrationalforce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR reviews are time-consuming and error-prone, and teams often miss structural issues or governance checks during merges. This Skill automates diff analysis against the base branch, runs governance prompts, and surfaces actionable recommendations to speed up safe merges.

Core Features & Use Cases

  • Automated diff analysis against the base branch to surface potential issues.
  • LLM-trust governance: enforce prompts and confirm safety boundaries before applying changes.
  • Proactive merge guidance: propose deterministic fixes and structured questions for complex decisions.
  • Use Case: When reviewing a PR, run this Skill to automatically surface critical issues and suggested fixes, reducing review time.

Quick Start

Run the current branch through the review workflow to obtain a structured set of issues and recommended actions.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate PR reviews to check for SQL safety and code quality?

Automated code review analyzes branch diffs against the base to surface structural issues, SQL safety risks, and code quality concerns, providing actionable recommendations for safer merges.

What is LLM trust boundary governance in automated code review?

LLM trust governance enforces prompts and confirms safety boundaries before applying automated changes during diff analysis, ensuring LLM-assisted reviews do not introduce unverified risks.

How do I analyze a branch diff for conditional side effects before merging?

Analyzing branch diffs for conditional side effects involves comparing current branches against the base to detect structural risks and surface actionable recommendations before merging.

Does automated diff analysis provide auto-fixes for complex merge decisions?

Automated diff analysis provides deterministic auto-fixes where safe and uses structured AskUserQuestion prompts to handle complex decisions, ensuring guided merge outcomes.

Can I use automated PR review for governance checks on structural code issues?

Automated PR review runs governance prompts during diff analysis to catch structural issues and quality concerns, reducing manual checks and speeding up safe merges.