Analyze pull request diffs for SQL safety, LLM trust boundaries, and side effects.
npx skills add https://github.com/shhubbh/flowstate --skill review-shhubbh
Please help me install this Agent Skill. Skill: review Source: https://github.com/shhubbh/flowstate/tree/main/.claude/skills/gstack/review Command: npx skills add https://github.com/shhubbh/flowstate --skill review-shhubbh
Review processes often lack a consistent, thorough check of diffs against the base branch, leading to missed SQL safety issues, ambiguous LLM prompts, and overlooked side effects.
Inspect the current PR diff with this skill to receive a structured review and actionable recommendations.
High-intent search queries and answers about installing and using this skill.
To check a pull request diff for SQL safety issues, you analyze the PR changes against the base branch to identify potential violations before merging. This process surfaces SQL risks and provides structured, actionable feedback for code reviewers.
Reviewing LLM trust boundary violations involves analyzing pull request diffs to detect prompt injection risks and ambiguous LLM prompts. It surfaces these risks across AI-related changes, providing structured decision criteria and questions to raise before merging.
Performing a pre-landing code review on SQL-heavy repos requires analyzing diffs against the base branch to catch unintended side effects and SQL safety issues. It applies deterministic checks and test hints to ensure code quality before changes land.
Yes, automated PR review can find unintended side effects by analyzing the pull request diff against the base branch. It identifies conditional side effects and provides actionable recommendations to address them before merging the code.
Static analysis catches prompt injection risks in AI-related changes by applying structured checks to the pull request diff. It identifies LLM trust boundary violations and generates actionable questions to resolve them during the code review.
You need structured checks for pull request reviews when working with SQL-heavy repos or AI-related changes to ensure SQL safety and LLM trust boundaries are maintained. It provides deterministic steps and decision criteria to catch issues before merging.
anilveersingh1308Review pull request diffs against a base branch for risk and impact.
ImL1sReview git diffs, fix code issues, run test suites, and generate conventional commits.
hector-mannyAutomate Laravel project verification with environment, lint, test, and security checks.
kk20300113-pngAnalyze pull request diffs for SQL injection, LLM trust boundary, and structural issues.
