Analyze branch diffs against main for SQL safety and trust boundary risks.
npx skills add https://github.com/XDCIndia/SkyNet --skill review-xdcindia
Please help me install this Agent Skill. Skill: review Source: https://github.com/XDCIndia/SkyNet/tree/main/.claude/skills/gstack/review Command: npx skills add https://github.com/XDCIndia/SkyNet --skill review-xdcindia
PR reviews can be slow and error-prone; this skill analyzes the current branch's diff against main to identify SQL safety issues, LLM trust boundary violations, and other structural risks before merging.
Run the /review workflow on your branch to generate a structured set of findings and recommendations.
High-intent search queries and answers about installing and using this skill.
Automating pre-merge PR reviews involves analyzing your branch diff against main to identify SQL safety risks and LLM trust boundary violations. This skill uses a two-pass workflow with a checklist to generate structured findings and recommended remediations before code merge.
A pre-landing code review checklist catches SQL data-safety risks, LLM prompt integrity violations, and broader structural consistency issues. By analyzing branch diffs against main, it enforces data protection and trust boundaries to reduce regression risk before merge.
A two-pass code review workflow surfaces critical and informational findings by applying a predefined checklist to the current branch diff. It identifies SQL safety issues and LLM trust violations, outputting structured findings to guide developer remediation interactively.
Yes, you can use this automated code review across codebases with standard git workflows. It applies to pre-merge PR reviews by analyzing the diff between your current branch and main to check for data safety, prompt integrity, and structural consistency.
Checking LLM trust boundaries during a pre-merge code review prevents prompt integrity violations and unauthorized trust boundary crossings. Analyzing the branch diff ensures structural consistency and data safety, reducing regression risk before the code lands in the main branch.
The best way to identify SQL data-safety risks is by running an automated review on your current branch diff against main. This process applies a checklist to catch SQL safety issues, LLM trust violations, and structural problems, generating actionable remediation recommendations.
aimasteraccAnalyze branch diffs for SQL safety, trust boundaries, and side effects.
bizzybaeAnalyze branch diffs for SQL safety risks and LLM trust boundary violations.
tpgordon8Review pull request diffs against main for SQL and LLM trust issues.
jeisenbackIdentify structural issues in diffs against the base branch.
