What is the problem?
一份给新手的 Codex 代码人工审核清单，覆盖需求、差异、依赖、测试、安全、交付记录、项目边界和复核顺序。
Quick solution
Treat this as a Codex checklist issue. First confirm the environment, inputs, permissions, logs, and delivery boundary. Then use the linked deep guide for the full checklist before changing production code or promising a result.
Read the deep guideDetailed steps
- 原始需求是否保存完整，包括截图、报错、链接、仓库、分支和客户原话。
- 目标结果是否能用一句话复述。
- 交付标准是否明确，例如“按钮可点击”“接口返回正确数据”“移动端不遮挡内容”。
- 是否存在必须先问客户的问题，例如权限、环境、截止时间、设计稿、测试账号。
- Codex 改了哪些文件。
- 是否新增或删除了文件。
Commands or code
The source article does not include a copyable command block. Do not invent commands here; follow the diagnostic steps in the deep guide and validate changes in the real project environment.
Risk notes
Confirm the real project environment, account permissions, platform rules, and output quality before delivery. Do not ship AI-generated changes without human review, and do not claim indexing, income, deployment success, or ranking improvements without measured evidence.