Analyze pull request diffs for SQL safety and trust boundary risks.
npx skills add https://github.com/chriswestt/claude-skills --skill review-chriswestt
Please help me install this Agent Skill. Skill: review Source: https://github.com/chriswestt/claude-skills/tree/main/gstack/review Command: npx skills add https://github.com/chriswestt/claude-skills --skill review-chriswestt
Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when asked to "review this PR", "code review", "pre-landing review", or "check my diff". Proactively suggest when the user is about to merge or land code changes. (gstack)
Run the review on your current PR to receive a comprehensive pre-landing assessment.
High-intent search queries and answers about installing and using this skill.
Run a pre-landing code review by analyzing the PR diff against the base branch, which surfaces SQL safety issues, LLM trust boundary violations, and conditional side effects. The review provides actionable guidance on merge readiness and recommended next steps before you land code changes.
Diff analysis detects structural risks in a pull request by identifying SQL safety issues, LLM trust boundary violations, conditional side effects, and other structural problems. It ensures detection coverage and actionable guidance so you know the risk and recommended actions before merging.
You can check your PR diff for LLM trust boundary violations by running a pre-landing review. The analysis highlights potential trust boundary violations and conditional side effects against the base branch, providing proactive guidance on merge readiness and recommended next steps.
You need a risk assessment for your code changes when you are about to merge or land code. Proactively run a pre-landing PR review to catch SQL safety issues, LLM trust boundary violations, and conditional side effects before merging your pull request.
The pre-landing review works by analyzing your diff against the base branch without requiring specific dependencies. It applies to any pre-landing PR reviews, code reviews, or tasks involving checking diffs before merging to ensure structural issue detection.
The best way to catch SQL safety issues in a PR diff is using an automated pre-landing review. It analyzes the diff against the base branch to flag risky SQL changes and other structural issues, providing actionable guidance and recommended actions before merging.
bhianerdReview pull request diffs for SQL safety, LLM trust boundaries, and concurrency hazards.
singhianand23045Analyze code diffs for SQL safety, LLM trust boundaries, and conditional side effects.
dr-codeRun pre-release verification checks and write a versioned release assessment report.
adityasingh2400Analyze pull request diffs against the base branch for SQL safety and structural risks.
