AI 工具指南
Codex/Deep guide

Codex Codex Github 4 36

用 Codex 辅助改代码时，GitHub 负责留下可复查记录。新手应先学会分支、提交、PR、diff、检查结果和客户授权边界，再把 AI 修改用于练习或交付。

What is the problem?

用 Codex 辅助改代码时，GitHub 负责留下可复查记录。新手应先学会分支、提交、PR、diff、检查结果和客户授权边界，再把 AI 修改用于练习或交付。

Quick solution

Treat this as a Codex roadmap 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 guide

Detailed steps

  1. 记录：每一次改动都有提交和文件差异。
  2. 隔离：分支让练习改动不直接影响主线。
  3. 审核：PR 让你或客户可以逐行查看改动。
  4. 验证：CI、预览链接和评论可以把检查结果放在同一个地方。
  5. 从干净工作区开始，先运行 `git status`。
  6. 新建任务分支，分支名写清楚目的，例如 `fix/header-layout`。

Commands or code

## Summary
- Updated:
- Reason:
- Out of scope:

## Verification
- npm run lint:
- npm run build:
- Manual check:

## Risks / Follow-up
- Needs customer confirmation:
- Needs account or platform authorization:
- Not verified:

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.