commit

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
<!-- markdownlint-disable-file MD041 -->
STARTER_CHARACTER = 📌
<!-- markdownlint-disable-file MD041 -->
STARTER_CHARACTER = 📌

Commit Changes

提交变更

Process

流程

1. Review Changes

1. 审查变更

bash
git status
git diff HEAD
git diff --stat HEAD
Check for new untracked files:
bash
git ls-files --others --exclude-standard
bash
git status
git diff HEAD
git diff --stat HEAD
检查新的未跟踪文件:
bash
git ls-files --others --exclude-standard

2. Stage Files

2. 暂存文件

Add the untracked and changed files relevant to the current work.
Do NOT stage:
  • .env
    or credential files
  • Large binary files
  • Files unrelated to the current task
添加与当前工作相关的未跟踪文件和已更改文件。
请勿暂存:
  • .env
    或凭据文件
  • 大型二进制文件
  • 与当前任务无关的文件

3. Create Commit

3. 创建提交

Write an atomic commit message with a conventional commit tag:
  • feat:
    -- New capability or feature
  • fix:
    -- Bug fix
  • refactor:
    -- Code restructure without behavior change
  • docs:
    -- Documentation only
  • test:
    -- Test additions or fixes
  • chore:
    -- Build, CI, tooling changes
  • perf:
    -- Performance improvement
For monorepo changes spanning multiple packages, note the primary package in the scope:
text
feat(workflows): add DAG condition evaluator
fix(web): resolve SSE reconnection on navigation
refactor(isolation): simplify worktree resolution order
Commit message format:
text
tag(scope): concise description of what changed

[Optional body explaining WHY this change was made,
not just what changed. Include context changes that aren't
obvious from the diff.]

[Optional: Fixes #123, Closes #456]
编写带有约定式提交标签的原子化提交消息:
  • feat:
    -- 新能力或新功能
  • fix:
    -- Bug 修复
  • refactor:
    -- 在不改变行为的情况下重构代码
  • docs:
    -- 仅涉及文档
  • test:
    -- 新增或修复测试
  • chore:
    -- 构建、CI 或工具链变更
  • perf:
    -- 性能改进
对于跨越多个包的 monorepo 变更,请在 scope 中注明主要包:
text
feat(workflows): add DAG condition evaluator
fix(web): resolve SSE reconnection on navigation
refactor(isolation): simplify worktree resolution order
提交消息格式:
text
tag(scope): concise description of what changed

[Optional body explaining WHY this change was made,
not just what changed. Include context changes that aren't
obvious from the diff.]

[Optional: Fixes #123, Closes #456]

4. Capture AI Context Changes

4. 捕获 AI 上下文变更

If any AI context assets were modified in this commit, add a
Context:
section to the commit body:
text
feat(orchestrator): add retry logic for session recovery

Added exponential backoff when SDK subprocess crashes mid-session.
Previously a single crash would fail the entire workflow.

Context:
- Updated .claude/rules/orchestrator.md with retry conventions
- Added .claude/commands/debug-session.md for session state inspection
- Surfaced issue: mock.module() in retry tests needs isolated batch

Fixes #482
What counts as AI context changes:
  • .claude/rules/
    -- on-demand conventions added, updated, or removed
  • .claude/commands/
    -- slash commands created or modified
  • .claude/skills/
    -- slash commands created or modified
  • .llmdocs/
    -- reference docs added or updated
  • CLAUDE.md
    -- global rules changes
  • **/CLAUDE.md
    -- folder local rules changes
Git log is long-term memory for future sessions.
如果此提交修改了任何 AI 上下文资源,请在提交正文中添加
Context:
部分:
text
feat(orchestrator): add retry logic for session recovery

Added exponential backoff when SDK subprocess crashes mid-session.
Previously a single crash would fail the entire workflow.

Context:
- Updated .claude/rules/orchestrator.md with retry conventions
- Added .claude/commands/debug-session.md for session state inspection
- Surfaced issue: mock.module() in retry tests needs isolated batch

Fixes #482
哪些内容属于 AI 上下文变更:
  • .claude/rules/
    -- 新增、更新或移除按需加载的约定
  • .claude/commands/
    -- 创建或修改斜杠命令
  • .claude/skills/
    -- 创建或修改斜杠命令
  • .llmdocs/
    -- 新增或更新参考文档
  • CLAUDE.md
    -- 全局规则变更
  • **/CLAUDE.md
    -- 文件夹本地规则变更
Git log 是未来会话的长期记忆。