review

Pre-landing code review is automated by analyzing the diff between your feature branch and main to detect SQL safety issues. The process applies a structured checklist to evaluate diffs and outputs findings with specific remediation guidance for reviewers.

A two-pass diff analysis evaluates pull request changes against main in two structured stages using a checklist. This method identifies SQL safety issues, LLM trust boundary violations, and conditional side effects, guiding reviewers through generating actionable findings.

To check a pull request for LLM prompt boundary violations before merging, run a diff analysis against the main branch. The review workflow identifies trust boundary violations and conditional side effects, providing remediation guidance for each finding.

Yes, you can use a checklist-driven workflow to review code diffs for conditional side effects. The workflow requires a repository diff against main and a specific checklist file, utilizing interactive prompts to clarify edge cases during the evaluation process.

To run an automated diff analysis workflow, you need access to the repository diff against main and a checklist file located at a specific path within your project structure. The workflow outputs a findings report with remediation guidance based on this input.

Your pre-landing review workflow needs a checklist file to provide the structured evaluation criteria required for the two-pass diff analysis. Without this checklist file located at the specified path, the workflow cannot systematically detect SQL safety issues, LLM trust boundary violations, and conditional side effects.