bicameral-scan-branch

Drift detection in a git branch analyzes code changes to identify decisions affected by those modifications. It works by returning drifted, pending, and reflected statuses for decisions, helping you prioritize fixes before merging.

To audit code drift across an entire branch before merging, run a single-call branch drift audit. It analyzes decisions affected by changed files and returns drifted, pending, and reflected statuses to guide remediation and ensure alignment with product decisions.

Yes, you can audit drift using base_ref and head_ref inputs to define a specific range. The audit reports sweep_scope and range_size alongside the list of drifted decisions, enabling targeted prioritization before merge.

Branch drift auditing enforces grounding and sign-offs for decisions affected by code changes. This ensures that drifted decisions are properly remediated and aligned with established product decisions before the branch is merged.

The best way to find pending and reflected decisions during a code review is to run a scope-aware drift audit. It surfaces these statuses across all changed files in one call, streamlining pre-merge review and prioritization.