[{"data":1,"prerenderedAt":693},["ShallowReactive",2],{"blog-claude-code-workflow-guide":3},{"id":4,"title":5,"body":6,"category":680,"date":681,"description":16,"extension":682,"meta":683,"navigation":507,"path":684,"seo":685,"stem":686,"tags":687,"__hash__":692},"blog\u002Fblog\u002Fclaude-code-workflow-guide.md","Claude Code 实战指北：从命令到工作流的效率密码",{"type":7,"value":8,"toc":664},"minimark",[9,13,17,25,28,33,36,129,135,139,143,155,164,182,192,195,198,226,231,234,237,282,288,292,299,359,375,380,384,390,393,398,413,419,424,428,431,441,445,451,454,458,465,598,616,621,624,627,650,653,660],[10,11,5],"h1",{"id":12},"claude-code-实战指北从命令到工作流的效率密码",[14,15,16],"p",{},"用 Claude Code（后称 CC）的第一个月，最容易犯的错误不是\"用不好\"，而是\"把它当 ChatGPT 用\"。",[14,18,19,20,24],{},"ChatGPT 是你问它答，CC 是它会真的改你的代码、跑你的命令、操作你的文件系统。把脑中的问题描述清楚丢给它，它自己能 Read → Edit → Bash → 验证，一条龙跑完。但前提是：",[21,22,23],"strong",{},"你得知道怎么驾驭它","。",[14,26,27],{},"这篇从最核心的命令讲起，覆盖模型调度、Plan 模式、Thinking 机制和日更工作流——读完你 80% 的日常操作都能脱手完成。",[29,30,32],"h2",{"id":31},"_1-四种输入前缀决定走哪条路","1. 四种输入前缀：决定\"走哪条路\"",[14,34,35],{},"CC 的输入框看似简单，但前缀是关键路由：",[37,38,39,55],"table",{},[40,41,42],"thead",{},[43,44,45,49,52],"tr",{},[46,47,48],"th",{},"前缀",[46,50,51],{},"作用",[46,53,54],{},"例子",[56,57,58,82,100,118],"tbody",{},[43,59,60,67,70],{},[61,62,63],"td",{},[64,65,66],"code",{},"\u002F",[61,68,69],{},"斜杠命令或 Skill：调用内建命令",[61,71,72,75,76,75,79],{},[64,73,74],{},"\u002Fclear","、",[64,77,78],{},"\u002Fcompact",[64,80,81],{},"\u002Freview",[43,83,84,89,92],{},[61,85,86],{},[64,87,88],{},"@",[61,90,91],{},"文件\u002F目录引用：把内容注入上下文",[61,93,94,75,97],{},[64,95,96],{},"@src\u002Fserver.ts",[64,98,99],{},"@docs\u002F",[43,101,102,107,110],{},[61,103,104],{},[64,105,106],{},"!",[61,108,109],{},"直接执行 shell，不走 Agent 推理",[61,111,112,75,115],{},[64,113,114],{},"!git status",[64,116,117],{},"!pnpm test",[43,119,120,123,126],{},[61,121,122],{},"无前缀",[61,124,125],{},"自然语言任务，交给 Agent",[61,127,128],{},"\"把 X 模块的日志改成结构化日志\"",[14,130,131,132,134],{},"一个容易被忽略的技巧：",[64,133,106],{}," 跑出来的结果会自动进入上下文，比让 Agent \"跑一下 git status\" 省一次工具调用往返。",[29,136,138],{"id":137},"_2-真正每天都会用的命令按频次排序","2. 真正每天都会用的命令（按频次排序）",[140,141,142],"h3",{"id":142},"会话管理",[14,144,145,147,148,75,151,154],{},[64,146,74],{},"（别名 ",[64,149,150],{},"\u002Freset",[64,152,153],{},"\u002Fnew","）是最高频命令——换任务前必做，清空上下文但保留 CLAUDE.md。上下文是 CC 最贵的资源，上一个任务的残留不仅费 token，还会干扰后续判断。",[14,156,157,160,161,24],{},[64,158,159],{},"\u002Fcompact [可选指令]"," 用于任务还要继续但上下文快爆时。可以传指令指定保留什么，比如 ",[64,162,163],{},"\u002Fcompact 只保留对支付模块的决策",[14,165,166,169,170,173,174,177,178,181],{},[64,167,168],{},"\u002Fresume"," 恢复历史会话（跨天长任务必备），",[64,171,172],{},"\u002Fbranch"," 从当前对话分叉做 A\u002FB 探索，",[64,175,176],{},"\u002Frewind"," 则比 ",[64,179,180],{},"git reset"," 更稳——会话和工作区一起回滚。",[14,183,184,187,188,191],{},[64,185,186],{},"\u002Fcost"," 在大改动前后各看一次，建立成本直觉。",[64,189,190],{},"\u002Fcontext"," 可视化当前上下文占用，调预算时第一时间看。",[140,193,194],{"id":194},"模型与成本三轴",[14,196,197],{},"CC 给了三个独立的旋钮控制速度\u002F成本\u002F质量：",[199,200,201,210,218],"ul",{},[202,203,204,209],"li",{},[21,205,206],{},[64,207,208],{},"\u002Fmodel","：Opus 4.7（架构难题）→ Sonnet 4.6（日常实现）→ Haiku 4.5（批量简单任务）",[202,211,212,217],{},[21,213,214],{},[64,215,216],{},"\u002Feffort low|medium|high|xhigh|max","：任务级努力档，Opus 默认 xhigh，Sonnet 上限 max",[202,219,220,225],{},[21,221,222],{},[64,223,224],{},"\u002Ffast","：用 Opus 4.6 + 跳过部分推理特效，简单任务显著降本",[14,227,228],{},[21,229,230],{},"经验：写代码的活用普通模式，想\"怎么写\"的活用 thinking 模式。",[140,232,233],{"id":233},"那些让你效率翻倍的非命令技巧",[14,235,236],{},"这些比很多命令都重要：",[199,238,239,245,251,257,267,273],{},[202,240,241,244],{},[21,242,243],{},"Esc","：方向跑偏立刻打断。比等它跑完再纠正便宜十倍。",[202,246,247,250],{},[21,248,249],{},"双击 Esc","：回到更早一条消息，从那里分叉——等于\"读档重来\"。",[202,252,253,256],{},[21,254,255],{},"Shift+Tab","：在六档 permission mode 间循环。",[202,258,259,262,263,266],{},[21,260,261],{},"Ctrl+B","：把当前任务塞后台跑（",[64,264,265],{},"\u002Ftasks"," 看进度）。",[202,268,269,272],{},[21,270,271],{},"拖入图片","：架构图、报错截图、Figma 截图直接拖进终端，CC 会识别。",[202,274,275,281],{},[21,276,277,280],{},[64,278,279],{},"\\"," + Enter","：多行输入（所有终端通用），粘长日志必备。",[14,283,284,287],{},[21,285,286],{},"小结："," 这些命令和快捷键是肌肉记忆级别的操作。玩熟之后，你会发现自己越来越少\"等 CC 跑完才发现方向错了\"——Esc 让纠偏成本趋近于零。",[29,289,291],{"id":290},"_3-thinking-关键字最被低估的能力","3. Thinking 关键字：最被低估的能力",[14,293,294,295,298],{},"任务描述里包含特定关键字，CC 会分配更多内部推理 token。注意这和 ",[64,296,297],{},"\u002Feffort"," 是两套机制——thinking 关键字调\"单回合推理深度\"，effort 调\"任务级努力档位\"，可叠加：",[37,300,301,314],{},[40,302,303],{},[43,304,305,308,311],{},[46,306,307],{},"关键字",[46,309,310],{},"大致预算",[46,312,313],{},"适用",[56,315,316,329,342],{},[43,317,318,323,326],{},[61,319,320],{},[64,321,322],{},"think",[61,324,325],{},"~4K tokens",[61,327,328],{},"简单分析",[43,330,331,336,339],{},[61,332,333],{},[64,334,335],{},"think hard",[61,337,338],{},"~10K tokens",[61,340,341],{},"中等复杂",[43,343,344,353,356],{},[61,345,346,349,350],{},[64,347,348],{},"think harder"," \u002F ",[64,351,352],{},"ultrathink",[61,354,355],{},"~32K tokens",[61,357,358],{},"架构设计、难 bug、并发问题",[14,360,361,364,365,367,368,371,372,374],{},[21,362,363],{},"取舍法则","：架构设计、并发\u002F一致性问题 → ",[64,366,352],{}," + ",[64,369,370],{},"\u002Feffort xhigh","；普通重构、写单测 → 不加关键字，甚至可以开 ",[64,373,224],{},"。思考越深越贵越慢，不是默认开越好。",[14,376,377,379],{},[21,378,286],{}," 把 thinking 关键字当成\"深度开关\"——只在真正需要推理深度的场景打开。日常编码任务不需要，省下的 token 比你想的多。",[29,381,383],{"id":382},"_4-plan-模式资深工程师最该用起来的功能","4. Plan 模式：资深工程师最该用起来的功能",[14,385,386,387,24],{},"进入方式：Shift+Tab 循环到 plan（最推荐），或 ",[64,388,389],{},"\u002Fplan [task description]",[14,391,392],{},"进入 plan 模式后，CC 只能用 Read\u002FGrep\u002FGlob 等只读工具，产出一份结构化实施计划。你 review 完、纠正方向后，accept plan 才会真的进 Agent 模式改代码。",[14,394,395],{},[21,396,397],{},"什么任务必走 Plan 模式？",[399,400,401,404,407,410],"ol",{},[202,402,403],{},"涉及 3 个以上文件或跨模块的改动",[202,405,406],{},"有架构选型空间的（\"加缓存\"——Redis？进程内？这时该规划）",[202,408,409],{},"你自己也没完全想清楚的需求",[202,411,412],{},"对生产行为有影响的（迁移、回滚、schema 变更）",[14,414,415,418],{},[21,416,417],{},"反模式","：已经完全想清楚的一行代码改动也走 Plan 模式——纯浪费时间。",[14,420,421,423],{},[21,422,286],{}," Plan 模式是让 CC 从\"码农\"变成\"架构师搭档\"的关键功能。它强制 CC 先思考再动手，而你在它动手前还有一次纠偏机会——这比事后回滚高效得多。",[29,425,427],{"id":426},"_5-推荐的日更工作流","5. 推荐的日更工作流",[140,429,430],{"id":430},"实现新需求",[432,433,438],"pre",{"className":434,"code":436,"language":437},[435],"language-text","1. \u002Fclear                              # 干净上下文\n2. 描述需求 + @相关目录 + \"进入 plan 模式\"\n3. CC 产出计划 → 你 review、纠偏、补充约束\n4. Accept plan → Agent 自动执行\n5. 执行中：看到偏了立刻 Esc；需要补文档 @具体文件\n6. 让它 \u002Freview 自查\n7. !pnpm test && !pnpm lint            # 直接 shell 跑验证\n8. 让 CC 基于 diff 写 commit message 草稿\n9. \u002Fcost 记录成本，\u002Fclear 准备下个任务\n","text",[64,439,436],{"__ignoreMap":440},"",[140,442,444],{"id":443},"查-bug","查 Bug",[432,446,449],{"className":447,"code":448,"language":437},[435],"1. \u002Fclear\n2. 贴报错日志 + 复现步骤 + \"ultrathink，先只分析不要改代码\"\n3. CC 输出若干根因假设 + 验证方法\n4. 你选最像的 → \"按假设 2 继续验证，允许读代码、跑测试，但不改代码\"\n5. 确认根因后：\"现在按最小改动修复，附带回归测试\"\n6. \u002Freview → 验证 → 提交\n",[64,450,448],{"__ignoreMap":440},[14,452,453],{},"这套两段式（先假设 → 再验证）比直接让它修 bug 效果好得多。资深工程师自己查 bug 也是这么想的，只是把这个过程显式化给了 CC。",[29,455,457],{"id":456},"_6-headless-模式把-cc-嵌入自动化","6. Headless 模式：把 CC 嵌入自动化",[14,459,460,461,464],{},"除了交互式，CC 还可以 ",[64,462,463],{},"claude -p \"\u003Cprompt>\""," 以非交互方式跑，适合 CI、cron、pre-commit hook 等场景：",[432,466,470],{"className":467,"code":468,"language":469,"meta":440,"style":440},"language-bash shiki shiki-themes github-dark","# 基础用法\nclaude -p \"检查这段 diff 有没有引入 N+1 查询\" --output-format stream-json\n\n# CI 安全用法（限制工具和轮数）\nclaude -p \"review 这个 PR 的安全问题\" \\\n  --allowedTools \"Read,Grep,Bash(git log:*)\" --max-turns 5\n\n# 极简启动（跳过所有扩展，脚本场景下显著快）\nclaude --bare -p \"...\"\n\n# 预算护栏，超了直接退\nclaude -p --max-budget-usd 2.00 --max-turns 10 \"...\"\n","bash",[64,471,472,481,502,509,515,528,543,548,554,567,572,578],{"__ignoreMap":440},[473,474,477],"span",{"class":475,"line":476},"line",1,[473,478,480],{"class":479},"sAwPA","# 基础用法\n",[473,482,484,488,492,496,499],{"class":475,"line":483},2,[473,485,487],{"class":486},"svObZ","claude",[473,489,491],{"class":490},"sDLfK"," -p",[473,493,495],{"class":494},"sU2Wk"," \"检查这段 diff 有没有引入 N+1 查询\"",[473,497,498],{"class":490}," --output-format",[473,500,501],{"class":494}," stream-json\n",[473,503,505],{"class":475,"line":504},3,[473,506,508],{"emptyLinePlaceholder":507},true,"\n",[473,510,512],{"class":475,"line":511},4,[473,513,514],{"class":479},"# CI 安全用法（限制工具和轮数）\n",[473,516,518,520,522,525],{"class":475,"line":517},5,[473,519,487],{"class":486},[473,521,491],{"class":490},[473,523,524],{"class":494}," \"review 这个 PR 的安全问题\"",[473,526,527],{"class":490}," \\\n",[473,529,531,534,537,540],{"class":475,"line":530},6,[473,532,533],{"class":490},"  --allowedTools",[473,535,536],{"class":494}," \"Read,Grep,Bash(git log:*)\"",[473,538,539],{"class":490}," --max-turns",[473,541,542],{"class":490}," 5\n",[473,544,546],{"class":475,"line":545},7,[473,547,508],{"emptyLinePlaceholder":507},[473,549,551],{"class":475,"line":550},8,[473,552,553],{"class":479},"# 极简启动（跳过所有扩展，脚本场景下显著快）\n",[473,555,557,559,562,564],{"class":475,"line":556},9,[473,558,487],{"class":486},[473,560,561],{"class":490}," --bare",[473,563,491],{"class":490},[473,565,566],{"class":494}," \"...\"\n",[473,568,570],{"class":475,"line":569},10,[473,571,508],{"emptyLinePlaceholder":507},[473,573,575],{"class":475,"line":574},11,[473,576,577],{"class":479},"# 预算护栏，超了直接退\n",[473,579,581,583,585,588,591,593,596],{"class":475,"line":580},12,[473,582,487],{"class":486},[473,584,491],{"class":490},[473,586,587],{"class":490}," --max-budget-usd",[473,589,590],{"class":490}," 2.00",[473,592,539],{"class":490},[473,594,595],{"class":490}," 10",[473,597,566],{"class":494},[14,599,600,603,604,607,608,611,612,615],{},[21,601,602],{},"安全红线","：headless 场景务必限制 ",[64,605,606],{},"--allowedTools"," 和 ",[64,609,610],{},"--max-turns","，防止跑飞。",[64,613,614],{},"--dangerously-skip-permissions"," 在生产\u002FCI 严禁——社区有过事故，等价于把仓库写权限给 prompt 注入者。",[14,617,618,620],{},[21,619,286],{}," Headless 模式把 CC 从一个\"交互式助手\"升级为\"可编程的工程能力\"。CI review、自动打 label、告警分流——这些场景的 ROI 极高。",[29,622,623],{"id":623},"总结",[14,625,626],{},"三个核心认知：",[399,628,629,635,644],{},[202,630,631,634],{},[21,632,633],{},"CC 是 Agent，不是 Chatbot","。它有一整套工具（Read\u002FEdit\u002FBash\u002FGrep\u002FTask），你给它什么上下文、什么规则，它就在什么边界里干活。",[202,636,637,24,640,643],{},[21,638,639],{},"速度\u002F成本\u002F质量是三轴可调的",[64,641,642],{},"\u002Fmodel × \u002Feffort × \u002Ffast","，学会这三个旋钮比纠结 prompt 写法重要。",[202,645,646,649],{},[21,647,648],{},"Plan 模式 + Esc 中断 = 最小纠偏成本","。让 CC 先想再动手，走偏了立刻打断——这套节奏一旦形成，效率是指数级的提升。",[14,651,652],{},"命令会迭代，但这个三轴调度的思路不会变。把基础操作练成肌肉记忆，把思考留给架构决策。",[14,654,655],{},[656,657,659],"a",{"href":658},"\u002Fblog\u002F","返回博客列表",[661,662,663],"style",{},"html pre.shiki code .sAwPA, html code.shiki .sAwPA{--shiki-default:#6A737D}html pre.shiki code .svObZ, html code.shiki .svObZ{--shiki-default:#B392F0}html pre.shiki code .sDLfK, html code.shiki .sDLfK{--shiki-default:#79B8FF}html pre.shiki code .sU2Wk, html code.shiki .sU2Wk{--shiki-default:#9ECBFF}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"title":440,"searchDepth":483,"depth":483,"links":665},[666,667,672,673,674,678,679],{"id":31,"depth":483,"text":32},{"id":137,"depth":483,"text":138,"children":668},[669,670,671],{"id":142,"depth":504,"text":142},{"id":194,"depth":504,"text":194},{"id":233,"depth":504,"text":233},{"id":290,"depth":483,"text":291},{"id":382,"depth":483,"text":383},{"id":426,"depth":483,"text":427,"children":675},[676,677],{"id":430,"depth":504,"text":430},{"id":443,"depth":504,"text":444},{"id":456,"depth":483,"text":457},{"id":623,"depth":483,"text":623},"AI\u002FLLM","2026-05-03","md",{},"\u002Fblog\u002Fclaude-code-workflow-guide",{"title":5,"description":16},"blog\u002Fclaude-code-workflow-guide",[688,689,690,691],"Claude Code","AI编程","开发工具","工作流","0zwVU1VHv8WLoopdi-S0fJszR6OLMlV1UriPERp6b0s",1779959652907]