Identify SQL safety, LLM trust boundaries, and side effects in branch diffs.
npx skills add https://github.com/mr-daedalium/ostack --skill review-mr-daedalium
Please help me install this Agent Skill. Skill: review Source: https://github.com/mr-daedalium/ostack/tree/main/review Command: npx skills add https://github.com/mr-daedalium/ostack --skill review-mr-daedalium
Pre-landing PR review automates the detection of SQL safety issues, LLM trust boundary violations, conditional side effects, and other structural risks in diffs between the feature branch and the base branch. Proactively surface guidance for merge readiness and provide concrete remediation suggestions.
Run the review skill on a PR branch to generate a pre-landing review report.
High-intent search queries and answers about installing and using this skill.
Automating pre-landing PR review involves analyzing the diff between your current branch and base branch to identify SQL safety issues, LLM trust boundary violations, and conditional side effects. The process generates an actionable report with proposed fixes and escalation prompts.
LLM trust boundary violations involve the potential leakage of prompts or sensitive information within code changes. Validating these boundaries during PR review detects structural risks early, ensuring sensitive data remains protected before code lands.
Checking for race conditions and side effects requires diff-scoped analysis of touched files to detect conditional side effects and structural risks. This surfaces high-risk patterns across modified files, providing actionable remediation suggestions for merge readiness.
AI code review detects SQL safety issues by validating queries and data modifications against best practices within the feature branch diff. It proactively surfaces high-risk SQL patterns and provides concrete remediation suggestions before merging.
A two-pass workflow for diff analysis first surfaces actionable findings, then generates fixed-first remediation suggestions. This approach ensures critical issues are identified before proposing concrete fixes, streamlining merge readiness decisions.
Pre-landing code review is needed when your feature branch contains SQL modifications, LLM integrations, or logic with potential side effects. It proactively surfaces structural risks and provides escalation prompts to ensure safe merge decisions.
kage1020Analyze branch changes and generate a five-section Markdown diff report.
leadmind-aiAudit codebases for pre-deployment risks and generate severity-sorted findings reports.
bennybennisonRun sequential build, type, lint, test, security, and diff checks.
yanochka11Analyze repository diffs to identify defects, security risks, and structural problems.
