Interview Bank

Mastering Claude: From Conversation to Claude Code in 5 Days

D3 Getting Started With Claude Code and Managing Context: Install, Writing CLAUDE.md and "Trim Until You Can't", Permission Modes, Plan Mode's "Explore, Then Plan, Then Write", /clear /compact /rewind, Giving Claude a Verifiable Check

• Why is 'give Claude a check it can run' the dividing line for using agents well, and what levels of enforcement can that check have?为什么说「给 Claude 一个可验证的检查」是用好 Agent 的分水岭？检查可以有哪几档硬度？

  Common in ChinaCommon overseasIntermediate#verification#agent-loop

  How to reason about it · think before answering

  1. This tests understanding of the agent loop. 'Tests matter' is common sense; explain where the loop closes without a check.
  2. Chain: an agent works in a do–observe–adjust loop and stops on 'looks done'. Without a runnable check, 'looks done' is the only signal and the verification step falls on you — every mistake waits to be noticed; present, it is a tool, absent, it is a risk. With a check (tests, build exit code, lint, diff-against-fixture, screenshot compare) the loop closes inside the machine: it works, runs, reads, and iterates to green while you review evidence.
  3. Four levels: in the prompt ('run the tests until they pass') — usable today; as a /goal — an independent evaluator re-checks every turn; as a Stop hook — the turn cannot end until the check passes, deterministic; as a reviewer subagent — the one who did the work is not the one grading it. Each step trades setup for attention.
  4. Production nuance: demand evidence, not claims — test output, commands and return values, screenshots; reviewing evidence beats re-running.
  5. Follow-up: can the check itself be gamed? Yes — the model might edit tests to pass. Counter with a deny rule on the test directory or a reviewer specifically checking for test tampering.

  分析过程 · 先想清楚再作答

  1. 这题考对 Agent 循环的理解。答成「测试很重要」是常识；要说清没有检查时循环在谁那里闭合。
  2. 推导：Agent 在「做、看结果、改」的循环里工作，停下来的信号是「看起来做完了」。没有可运行的检查，「看起来做完了」是唯一信号，验证环落在人身上——每个错误都要等你注意到，你在场它是工具，你不在场它是风险。有了检查（测试、构建退出码、lint、比对脚本、截图对照），循环在机器里闭合：它做、它跑、它读结果、它改到通过，你只审证据。
  3. 硬度分四档：写进提示词（「实现后跑 pnpm test 直到全过」）——今天就能用；设为 /goal——独立评估器每轮复核直到达成；写成 Stop hook——测试不过不允许结束，确定性门禁；交给另一个 subagent 复核——做的人和判的人分开。每升一档多一点配置，换来少一点盯着。
  4. 生产视角：要求展示证据而不是宣布成功——贴测试输出、贴命令与返回值、贴截图；审证据比自己重跑快。
  5. 可预期的追问：检查本身会不会被绕过？会——模型可能改测试让它过。对策是把测试目录放进禁改清单，或让 reviewer subagent 专门核对「有没有为了过而改测试」。

  Key points

  • Without a check the loop closes on you; with one it closes inside the machine
  • A check is anything with a pass/fail signal: tests, build, lint, fixture diff, screenshot compare
  • Four levels: prompt instruction, /goal re-evaluation, Stop hook gate, independent reviewer subagent
  • Demand evidence over claims; guard against test tampering with deny rules or a dedicated reviewer

  答题要点

  • 没有检查时循环在人身上闭合，每个错误都等你发现；有检查时循环在机器里闭合
  • 检查可以是测试、构建、lint、比对脚本、截图对照，任何能产生通过/失败信号的东西
  • 四档硬度：提示词里要求、/goal 每轮复核、Stop hook 确定性门禁、subagent 独立复核
  • 要证据不要宣言；防止改测试作弊要靠禁改清单或专门的复核