37/41 · Part 6 · 跟 Agent · build → verify

Agent · 最后一条最重要

"Build" 不等于 "Done"。
让 agent 自己跑 verify。

反例

Build → Claim done

"我做完了 X 功能 ✓"——但没跑测试、没 grep 验证、没 curl bundle 看是否真部署上去。

真实事故：2026-06-02 final-stream vs last-cigarette 同 UUID 撞车 · 2026-05-31 sweep 用 grep -l 漏 vital-signs · push 成功 ≠ deploy 成功

正解

Build → Verify → Ship

Pre-ship 5 道 grep checkpoint：

grep -L 找缺失，不是 -l 找存在
Edit 后 grep 文件再 git add（防 stale no-op）
git -C abs-path，cwd 会漂
curl bundle URL 验证新 class 在不在
UUID 唯一性脚本通过

让 agent 走完 verify 再说 "done" · pre-ship-verify skill

Agents · the last rule is the most important

"Build" doesn't mean "Done".
Make the agent verify itself.

anti-pattern

Build → Claim done

"I shipped feature X ✓" — no tests run, no grep verification, no curl on the bundle to confirm the deploy.

Real incidents: 2026-06-02 final-stream vs last-cigarette shared a UUID · 2026-05-31 sweep using grep -l missed vital-signs · push success ≠ deploy success.

correct path

Build → Verify → Ship

Pre-ship 5-grep checklist:

grep -L finds absence, not -l for presence
Grep edited file after every Edit before git add (defends stale no-op)
git -C abs-path — cwd drifts
curl bundle URL to confirm the new class is in
UUID uniqueness script passes

Ship only after verify · pre-ship-verify skill

备忘 · 按 S 关闭Notes · S to close

这一张钉死整个 "agent 沟通"章的硬底线。讲的时候让同学问自己—— "我让 agent 做完事，我有没有让它验证？还是只接受了它说的 'done'？"

5 道 grep 是 2026-05-31 一整天踩坑后总结。Push 成功不等于 deploy 成功，这条具体可以演示：找一个游戏的 bundle URL，curl 一下看有没有最新 class，让同学体感。

Hard bottom line for the whole "talking to your agent" chapter. Ask the room: "When my agent says 'done,' did I make it verify? Or did I accept the claim?"

The 5 greps came out of a full day of failures on 2026-05-31. Push success ≠ deploy success — demonstrate live by curl'ing a game's bundle URL to check for a recently shipped class. Let the room feel the gap.