Analyze diffs against the base branch for SQL safety and trust boundary risks.
npx skills add https://github.com/filipnyquist/caidos --skill review-filipnyquist
Please help me install this Agent Skill. Skill: review Source: https://github.com/filipnyquist/caidos/tree/main/.claude/skills/gstack/review Command: npx skills add https://github.com/filipnyquist/caidos --skill review-filipnyquist
Pre-landing PR reviews are error-prone and time-consuming. This skill streamlines the process by analyzing diffs for critical risks such as SQL safety, LLM trust boundary violations, and conditional side effects, helping reviewers catch issues early.
Provide the current diff against the base branch to begin an automated pre-landing review.
High-intent search queries and answers about installing and using this skill.
Automated PR review for SQL safety and LLM trust boundaries works by analyzing your diff against the base branch to surface injection risks, trust breaches, and side effects, generating a remediation plan for reviewers.
Pre-landing diff analysis evaluates code changes before merging to detect risks like unsafe SQL interpolations, LLM trust boundary violations, and conditional side effects. It provides clear risk flags to guide reviewers through remediation and decision points.
To check a diff for SQL injection risks before landing a PR, provide the current diff against the base branch. The analysis highlights potential unsafe interpolations and prompts for additional tests to ensure database query safety.
Yes, automated code review works for catching unintended side effects by analyzing diffs against the base branch. It targets conditional side effects and trust boundary breaches, providing clear signals for potential risks and improvement opportunities.
Yes, you can use diff analysis to enforce LLM trust boundaries in code reviews. The skill checks that prompts and outputs stay within safe, auditable boundaries, flagging trust boundary violations for remediation before landing.
No, you do not need to provide the full repository to run a pre-landing code review. You only need to provide the current diff against the base branch to begin the automated analysis and receive risk flags.
AkbarDevopIdentify production-risk findings in a code diff before merging.
tan-yong-shengAnalyze PR diffs for SQL safety and LLM trust boundary issues.
wade56754Verify ad-code integration for cross-module boundary and API violations.
DevHive1Orchestrate dependency, static analysis, and privacy dataflow scanners into prioritized reports.
