reviewing-operations-premerge

A pre-merge PR review validates code quality and security before merging changes. It evaluates change consistency, commit messages, checks for sensitive data, and verifies dependency vulnerabilities using external review tools within the operations workflow.

Before merging operations code, security checks should scan for sensitive information inclusion, apply security reviews, and confirm dependency vulnerabilities. Pre-merge validation ensures operations changes meet security standards before integration.

Yes, external review tools such as Codex, Claude Code, or Gemini are required to automate pull request quality checks. The pre-merge review relies on this common reviewing infrastructure to evaluate code quality and security.

You can standardize code quality reviews for large pull requests by evaluating overall change consistency, commit message appropriateness, and detecting unnecessary changes. This promotes pre-approval from both code quality and security perspectives.

A pre-merge PR review should be executed during the Operations Phase before integrating changes. It applies to pull requests involving code quality updates, security checks, and documentation modifications.