Analyze PR diffs for SQL safety and structural risks.
npx skills add https://github.com/vib795/copilot-anatomy --skill review-vib795
Please help me install this Agent Skill. Skill: review Source: https://github.com/vib795/copilot-anatomy/tree/main/.github/skills/gstack-review Command: npx skills add https://github.com/vib795/copilot-anatomy --skill review-vib795
Pre-landing PR reviews are time-consuming and error-prone. This skill analyzes diffs against the base branch to surface SQL safety issues, LLM trust boundary violations, conditional side effects, and other structural risks before merging.
Review a PR by saying 'review this PR' or '/gstack-review' with the diff attached.
High-intent search queries and answers about installing and using this skill.
Pre-landing code review identifies SQL safety issues and LLM trust boundary violations by analyzing PR diffs against the base branch. It surfaces conditional side effects and structural risks before merging, providing structured actionable feedback to prevent risky deployments.
Diff analysis detects SQL safety issues, LLM trust boundary violations, and conditional side effects before merging. By evaluating pull request changes against project context, it proactively recommends fixes for structural risks found in data and logic modifications.
Run a diff check by attaching the pull request diff and providing the base branch and project context. The review analyzes the changes to surface conditional side effects and other structural risks, returning structured feedback with proactive suggestions before you merge.
Pre-landing PR review requires access to the diff, base branch, and project context to enforce safety checks. This environment setup allows the analysis to accurately identify SQL safety issues, LLM trust boundary violations, and structural risks across data and logic changes.
Reviewing code changes for LLM trust boundary violations is best handled by analyzing PR diffs against the base branch. This process evaluates structural risks across logic changes, enforcing safety checks and recommending fixes to prevent unintended model behavior before merging.
Automated diff checks should be used for pre-landing reviews when merging changes involving SQL, data, and logic modifications. They proactively surface structural risks and safety issues that manual code review might miss, ensuring consistent enforcement of trust boundaries before deployment.
YaugourtAnalyze code diffs for SQL safety, trust boundary, and side effect issues.
zizzfizzixAutomate code review for architectural, security, and quality compliance.
flutterIdentify and resolve Dart static analysis errors and runtime exceptions.
RedHatProductSecurityAutomate static code analysis for security vulnerabilities across multi-language repositories.
