Analyze PR diffs for SQL safety, LLM trust boundary violations, and conditional side effects.
npx skills add https://github.com/zz8011/harnesstest --skill review-zz8011
Please help me install this Agent Skill. Skill: review Source: https://github.com/zz8011/harnesstest/tree/main/.claude/skills/gstack/review Command: npx skills add https://github.com/zz8011/harnesstest --skill review-zz8011
Pre-landing PR review analyzes the diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. It proactively suggests when the user is about to merge or land code changes.
Provide the PR diff to the skill and let it run its checks to surface issues and recommendations.
High-intent search queries and answers about installing and using this skill.
To analyze a pull request diff for SQL safety issues, you provide the PR diff to a pre-landing review process that surfaces injection risks and structural issues before merging. It proactively detects vulnerabilities and offers actionable fix suggestions.
A pre-landing code review for LLM trust boundary violations analyzes your PR diff to detect unauthorized model permissions and conditional side effects. It proactively surfaces security risks before code changes are merged into the base branch.
Yes, you can use automated diff analysis to detect conditional side effects in a pull request. By evaluating the PR diff against the base branch, the review process identifies potential side effects and enforces proactive risk detection.
Pre-landing code review works without external dependencies or components. You simply provide the PR diff, and the standalone analysis mechanism runs its checks to surface SQL safety issues, LLM trust boundary violations, and structural risks.
You should run a pre-landing review instead of a standard post-merge code review because it analyzes PR diffs against the base branch to surface risks and offer actionable guidance before merging. This prevents vulnerable code from landing in the main repository.
The best way to perform a pre-landing PR review for merge readiness is to supply the PR diff for automated analysis. This process surfaces SQL safety issues, LLM trust boundary violations, and conditional side effects to ensure safer code integration.
rjernstCreate a GitHub pull request from the current branch with commit history and diff context.
mvillmowVerify GitHub pull requests for CI checks, approvals, and merge conflicts.
yanochka11Analyze repository diffs to identify defects, security risks, and structural problems.
aporto-techAnalyze code diffs for SQL safety and LLM trust boundary violations.
