skills.rest
devs6186
devs6186COMMUNITY
Explore all skills by this author →
GitHub

review

Analyze diffs for SQL safety and LLM trust boundary violations.

1|Updated Mar 19, 2026
Search Tags:#routing#risk-analysis#pr-review#diff-analysis#gstack#sql-safety#llm-trust
One-click install
npx skills add https://github.com/devs6186/claude-private-skills-agents-commands --skill review-devs6186
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/devs6186/claude-private-skills-agents-commands/tree/main/skills/gstack/review
Command: npx skills add https://github.com/devs6186/claude-private-skills-agents-commands --skill review-devs6186

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-landing PR review helps teams catch data safety, security, and structural issues before merging by analyzing the pull request diffs against the base branch, including SQL safety, LLM trust boundaries, and potential side effects.

Core Features & Use Cases

  • Analyzes diffs for SQL safety, LLM trust boundary violations, and conditional side effects to prevent risky changes from landing.
  • Provides proactive guidance and routing suggestions to improve code quality and security posture before merge.
  • Use Case: When a developer asks for a review of a PR or code diff, the skill returns structured findings and recommended next steps to guide the decision.

Quick Start

Provide a pre-landing PR review on the current diff and return actionable feedback.

Frequently Asked Questions about review

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

FAQPage Schema
What is pre-landing PR review for catching SQL safety and LLM trust boundary issues?▼

Pre-landing PR review analyzes pull request diffs against the base branch to catch data safety, security, and structural risks like SQL safety violations and LLM trust boundary compromises before merging.

How do I review code diffs for conditional side effects before merging in GitHub or GitLab?▼

You review code diffs by submitting the pull request or code changes to the skill, which returns structured findings, actionable guidance, and routing suggestions to prevent risky changes from landing.

Does gstack workflow support automated risk analysis for pull request diff routing?▼

Yes, the gstack workflow supports automated diff analysis and feedback by integrating pre-landing risk analysis to provide governance and routing suggestions for the reviewed code changes.

Can I use automated PR review for SQL safety checks in my continuous integration pipeline?▼

Yes, you can use this automated PR review approach to analyze SQL safety within your pipeline, returning actionable findings and recommended next steps to guide merge decisions.

What's the best way to analyze LLM trust boundary violations in code changes?▼

The best way to analyze LLM trust boundary violations is to perform a pre-landing diff analysis that identifies these structural risks and provides proactive guidance to improve your security posture before merge.

When should I not use automated pre-landing PR review for my code changes?▼

You should not rely solely on automated pre-landing PR review when you need deep semantic logic verification beyond structural risk, as it targets SQL safety, LLM trust boundaries, and conditional side effects in diffs.

Related Skills

Explore More Software Engineering Skills→
GenEducationGenEducation

review

Analyze pull-request diffs for defects and scope drift in GitHub or GitLab.

Official
Advanced
adryanmoldokkr32-pixeladryanmoldokkr32-pixel

review

Analyze PR diffs for SQL safety, trust boundary, and side-effect risks.

Community
Advanced
mattothomasmattothomas

review

Analyze PR diffs for SQL safety, LLM trust boundary violations, and side-effect risks.

Community
Intermediate
thkim2015thkim2015

moai-workflow-loop

Automates a feedback loop for code quality using LSP diagnostics and AST-grep.

Community
Advanced