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。