What is the problem?
给 AI 工具新手看的 Codex + GitHub 提交流程：确认工作区、创建分支、限定修改范围、查看 diff、运行检查、写提交说明、开 PR，并避免直接推主分支。
Quick solution
Treat this as a Codex tutorial 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`，确认工作区是否干净，是否有你不认识的改动。
- 创建任务分支，例如 `fix/button-spacing` 或 `draft/readme-cleanup`。
- 让 Codex 只读取和任务相关的文件，避免扩大范围。
- 修改后查看 `git diff`，逐项解释每个变化。
- 跑项目已有检查，例如 lint、build、测试、内容检查或页面 smoke test。
Commands or code
git status
git switch -c fix/example-task
git diff
npm run lint
npm run build
git add <files>
git commit -m "Fix example task"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.