Analyze PR diffs for SQL safety, LLM trust boundaries, and conditional side effects.
npx skills add https://github.com/rahmanayon/beehive --skill review-rahmanayon
Please help me install this Agent Skill. Skill: review Source: https://github.com/rahmanayon/beehive/tree/main/.claude/skills/gstack/review Command: npx skills add https://github.com/rahmanayon/beehive --skill review-rahmanayon
Diff-heavy PRs can introduce SQL safety issues, trust boundary violations in LLM outputs, and subtle structural problems that slip past tests. This Skill provides a focused pre-landing PR review by analyzing the diff against the base branch and surfacing actionable issues.
Run the review workflow on a pull request or diff using /review to surface issues and recommended actions.
High-intent search queries and answers about installing and using this skill.
You can automate PR reviews by analyzing code diffs against the base branch to detect SQL safety issues, LLM trust boundary violations, and conditional side effects. Running the review workflow surfaces actionable risks and recommended fixes before merging code changes.
A pre-landing PR review analyzes pull request diffs before merging to identify SQL safety issues, LLM trust boundary violations, and conditional side effects. You need it when diff-heavy changes risk introducing subtle structural problems that might slip past standard automated tests.
To check pull request diffs for conditional side effects, run a diff analysis workflow that compares changes against the base branch. This surfaces subtle structural risks and governance or policy violations, providing actionable recommendations before the code lands.
Yes, automated code review can guide routing and telemetry decisions during pull request analysis. The workflow evaluates diffs to ensure changes align with project standards, satisfying routing prompts, proactive suggestions, and plan-mode interactions through tool-enabled workflows.
Yes, the code review workflow specifically applies to base-branch comparisons by analyzing pull request diffs. It surfaces risks related to SQL safety, LLM trust boundaries, and conditional side effects across the changes detected between the feature branch and base.
Automated diff analysis focuses on detecting LLM trust boundary violations, SQL safety issues, and conditional side effects in pull request diffs. It serves as a pre-landing review to surface risks, but may not catch every nuanced logic error beyond its targeted analysis scope.
nexus-a1Analyze pull request diffs for quality and security issues.
shaythegay13Analyze PR diffs for SQL safety, LLM trust boundaries, and side effects.
zeronx798Scan staged git changes for security issues and quality regressions.
ajsai47Analyze git diffs for SQL injection, race conditions, and shell injection risks.
