productionos-review

Pre-landing risk review analyzes code diffs across branches to surface high-risk issues before merging. It checks SQL safety, trust boundaries, side effects, test coverage, and dependency risks to produce a prioritized findings list with severities and concrete remediation guidance.

Pre-landing code review is a deterministic process that evaluates pull request diffs for correctness and security risks before release. You need it when merging risky PRs that involve SQL changes, LLM trust boundaries, or new dependencies.

You can analyze SQL safety and LLM trust boundaries by running a pre-landing risk review on the changed files. The review assesses trust boundaries, conditional side effects, and dependency risks to generate an evidence-first findings report.

Yes, pre-landing risk review integrates with Codex-safe workflows to provide deterministic review ordering. It operates on diffs, branches, and changed files across repositories to output prioritized findings with file references and remediation guidance.

Yes, pre-landing risk review checks code diffs for missing tests and dependency risks alongside SQL safety and security issues. It produces a prioritized findings list with severities and evidence to support deterministic pre-landing review decisions.

Automated diff analysis for security review focuses on risk signals within the provided diff, branches, and changed files. It surfaces high-risk issues like side effects and trust boundaries but requires a pre-landing review workflow to ensure comprehensive coverage before merging.