agent-change-walkthrough

Generate one coherent implementation story that explains how the code works end-to-end after the change.

Never include conversation process, investigation history, or request negotiation as walkthrough steps. The walkthrough must describe implementation behavior only. Never include full file dumps, raw secrets, credentials, tokens, private keys, or copied production payloads in the final output.

If runtime order and dependency order conflict, prefer dependency order and add one short transition sentence that reconnects to runtime flow.

生成人工智能编写的代码更改（从运行时触发到最终行为）的单故事演练，将已更改和未更改的代码编织成一个叙述，并带有注释的差异、权衡、替代方案和风险分析。当被要求“解释发生了什么变化”、“引导我完成此差异”、“总结代理编辑”、“展示此功能如何工作”或“逐步解释此实现”时使用。 来源：cameroncooke/cameroncooke-skills。