Commit
Also: 提交 · commit message · git commit · 提交訊息 · 快照
One save: the project's entire state at one moment, recorded together with a note explaining it.
When you will meet it
An AI agent normally commits after each step, so you can undo its mistakes and see exactly which files it touched. Without this idea you watch an agent change a large swathe of your project with no way to separate its edits from what was already yours.
An analogy
Like 'save with a note' while writing: not another file cluttering the folder, but a timestamp stamped on the same document plus one line saying what changed here.
Minimal example
git add -A
git commit -m "把 API key 從程式碼移到環境變數"
git log --oneline # 4c380c5 把 API key 從程式碼移到環境變數
git show 4c380c5 # 這一次存檔究竟改了哪幾行A commit message is written for you in three months, and for your teammates. Ideally, reading git log alone tells you the project's history without opening files and comparing them one by one.
What people get wrong
- Writing messages like 'update', 'fix' or 'tweaked a bit'. When you need to roll back one specific change, such a message carries zero information — equivalent to no message at all.
- Stuffing ten unrelated changes into one commit. When you need to revert just one of them you cannot separate it any more — and agents frequently save half-finished work this way.