Analyze PR diffs for SQL safety, trust boundaries, and race conditions.
npx skills add https://github.com/0xHarbs/agent-setup --skill review-0xharbs
Please help me install this Agent Skill. Skill: review Source: https://github.com/0xHarbs/agent-setup/tree/main/claude/skills/lifecycle/review Command: npx skills add https://github.com/0xHarbs/agent-setup --skill review-0xharbs
Analyzes the current branch's diff against main to surface SQL safety issues, trust-boundary violations, race conditions, and other structural risks before merging, guiding engineers to address problems early.
To start a pre-landing PR review, run the /review workflow against the current branch.
High-intent search queries and answers about installing and using this skill.
Pre-landing PR safety checks analyze your branch diff against main to surface SQL safety, trust-boundary, and race-condition issues before merging. The review computes a two-pass analysis generating CRITICAL findings and INFORMATIONAL insights to guide remediation.
A two-pass code review identifies CRITICAL findings like SQL injection, concurrency, and trust-boundary violations in the first pass, then generates INFORMATIONAL insights for comprehensive PR documentation and acceptance criteria during the second pass.
Yes, the PR review workflow auto-detects your stack across Rails, Node, and Ruby repositories, loading the appropriate base and stack-specific checklists to perform accurate cross-file analysis and consistency checks across diffs.
You can analyze multi-repo code reviews by running the review workflow against your current branch. It computes structured findings with remediation guidance and acceptance criteria, ensuring main-branch stability is preserved across automated pipelines.
Pull request diff analysis flags trust-boundary violations because they represent structural risks that compromise security. The pre-landing review identifies these violations early alongside SQL safety and race-condition issues to ensure clean merges.
Automated PR diff analysis focuses on structural risks within the provided diff, generating acceptance criteria for handoff artifacts. It operates as a pre-landing safety check and does not replace runtime testing or dynamic concurrency analysis for complex race conditions.
AkbarDevopIdentify production-risk findings in a code diff before merging.
Mathews-TomAudit code diffs against a checklist and issue a landing verdict.
DariusCorvusAnalyze diffs for SQL safety, LLM trust boundaries, and conditional side effects.
a29paulDetects SQL injection, LLM trust boundary violations, race conditions, and enum gaps in pull request diffs.
