What is the problem?
一份给 AI 工具新手使用的 Codex 修 bug 检查清单,覆盖原始证据、工作区状态、修改范围、验证命令、回滚点、交付说明和人工复核。
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
- 是否保存了客户原始报错、截图、链接和复现步骤?
- 是否知道客户认为“修好”的标准?
- 是否确认当前分支和最新提交?
- 是否运行 `git status`,确认工作区有没有未解释的改动?
- 是否列出了本次允许修改的文件范围?
- 是否确认没有把客户密钥、账号、真实数据或生产日志交给工具?
Commands or code
请只基于脱敏材料分析这个 bug。
请优先给出最小修改方案,不要重构无关模块。
如果需要登录、授权、生产环境或真实数据,请停止并列出人工确认事项。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.