pre-landing-review

Run a pre-landing safety audit by supplying the branch diff and verifying the checklist. The process performs a two-pass triage to classify blocking or informational issues, yielding a final landing verdict with remediation guidance.

A two-pass safety triage evaluates diffs by first identifying critical blocking issues and then cataloging informational findings. This structured checklist approach enforces remediation before delivering a final merge verdict.

The gate review analyzes diffs against predefined criteria to identify blocking issues. It mandates remediation for critical findings and compiles explicit guidance for fixes or acknowledgments before allowing the merge.

You can customize the safety checklist by modifying the references file. The review loads its mandatory checklist from this file, allowing you to define the specific criteria used to gate code changes.

The best way to ensure a branch is safe to merge is performing a structured safety audit. This process analyzes diffs against a checklist, enforces blocking remediation for critical issues, and provides a final landing verdict.

When critical blocking issues are found during diff analysis, the safety audit enforces remediation. It prevents the merge and compiles explicit developer-facing guidance for required fixes or necessary acknowledgments.