A pull request should explain what changed, why it matters and how it was verified.
The practical workflow
Confirm the working branch, inspect the diff for accidental files and secrets, run formatting and relevant tests, and check failure cases. Write a PR summary with context, implementation details, test commands, screenshots where applicable and risks. Include rollback steps for data changes.
Copy-and-adapt prompt
Prepare a PR description from this diff and test output: [paste]. Separate confirmed test results from tests not run. Include changes, rationale, validation, risks and review questions. Do not invent a passing CI status.
Review checklist and limitations
Use repository branch protections and human review for production changes. Codex can assist with preparation but cannot guarantee the outcome of unrun tests.
What to do next
Choose a small issue, document the baseline and verify the result with a real test. Continue with the other Codex guides in the navigation menu.
Official documentation
OpenAI Codex documentation: https://developers.openai.com/codex/
