10 | Codex Review and GitHub PR: From Change to Merge

Review is the main gate before merge

The upstream guide places App Review at the center of the path from change to merge. It is not a second implementation explanation. It brings the task, Git state, diff, tests, and risk together so a person can judge whether the change is ready for a PR.

The Review panel reflects actual project Git state, not only what Codex has done. Existing working-tree changes, untracked files, and branch differences all belong in the judgment.

A complete change sequence

1. State the task and non-goals; form a plan.
2. Implement within a controlled scope.
3. Read the diff and confirm every unexpected modification.
4. Run relevant tests, builds, or manual checks.
5. Use /review to focus on findings, evidence, risk, and follow-up.
6. Prepare the PR description for GitHub collaborators.

Passing tests are one layer of evidence, not the whole review. Confirm requirement coverage, scope, edge cases, and rollback risk as well.

Read a diff in four layers

The course’s review approach can be summarized as task/scope match, business logic, test and verification coverage, then security, compatibility, and maintenance risk. Do not merely say that something is wrong; identify the location, impact, evidence, and smallest repair direction.

Hand the conclusion to the PR

GitHub Connector can provide repository and PR context, but it does not replace human approval. A PR description should at least preserve:

## Summary
What was done and what was intentionally not done.

## Verification
Checks run and their results.

## Risk
Assumptions, limits, or points still requiring human confirmation.

This handoff connects App work to GitHub review instead of leaving half the context in each system.