Analyze diffs against the base branch for SQL safety and structural risks.
npx skills add https://github.com/JonOlsenCa/gstack-main --skill review-jonolsenca
Please help me install this Agent Skill. Skill: review Source: https://github.com/JonOlsenCa/gstack-main/tree/main/review Command: npx skills add https://github.com/JonOlsenCa/gstack-main --skill review-jonolsenca
Pre-landing PR reviews are manual, error-prone and slow. This Skill automates the analysis of diffs against the base branch to surface issues such as SQL safety risks, LLM trust boundary violations, conditional side effects, and other structural problems before code lands.
Describe the PR to review and run the /review workflow to start the pre-landing review.
High-intent search queries and answers about installing and using this skill.
Automated pre-landing PR reviews analyze your diff against the base branch to surface SQL safety issues, LLM trust boundary violations, and conditional side effects before code lands. This process flags potential merge blockers and suggests concrete remediation steps.
An LLM trust boundary violation in a diff check occurs when untrusted input crosses into LLM processing without proper safeguards. Automated diff analysis proactively surfaces these structural risks along with SQL safety issues before merge.
Yes, automated PR review requires access to the repository diff and the gstack toolkit to function. These inputs allow the analysis to compare changes against the base branch and surface actionable insights for engineering teams.
To start a code review for merge blockers, describe the PR and run the review workflow. This initiates the pre-landing analysis to proactively flag structural risks and suggest fixes to improve ship confidence.
The best way to check diffs for conditional side effects is applying automated pre-landing analysis against the base branch. This proactively identifies structural problems and flags potential merge blockers with suggested remediation steps.
Yes, you can use diff analysis to support proactive guidance during PR discussions. By surfacing SQL safety risks and structural problems before code lands, engineering teams improve ship confidence and resolve issues faster.
allen-hsuIdentify critical issues in repository diffs against the base branch.
zz8011Analyze PR diffs for SQL safety, LLM trust boundary violations, and conditional side effects.
jm199seoAnalyze pull request diffs against the base branch for structural issues.
ajsai47Analyze git diffs for SQL injection, race conditions, and shell injection risks.
