review

Automated pre-landing PR review analyzes your branch diff against the base branch to surface SQL safety concerns, LLM trust boundary violations, and scope creep before merging. It maps active plan items to structural changes, marking them as DONE, PARTIAL, NOT DONE, or CHANGED.

Diff analysis in automated branch reviews compares the current branch against origin/main to identify risky structural changes and potential scope drift. It maps actionable plan items to specific code modifications, tracking completion status and highlighting side effects before the code lands.

To check LLM trust boundary violations before merging, run a pre-landing review workflow that analyzes your diff against the base branch. The audit identifies risky changes and side effects, providing a structured summary that reviewers can use to assess LLM trust and safety.

Yes, you can map active plan items to diff changes to track scope creep. The review workflow optionally leverages an active plan to extract actionable items, auditing them against the branch diff and reporting completion statuses to inform stakeholders of any scope drift.

Yes, the pre-landing risk audit works without a predefined plan by relying on diff-scoped analysis. While it optionally leverages an active plan to map actionable items, it independently compares the branch against origin/main to identify risky SQL changes and structural side effects.