📄 中文摘要
在一次工作流程中，仅因将提示中的“list”改为“enumerate”，导致了下游 JSON 解析器的故障，耗费了 40 分钟才找出问题所在。若有变更日志，解决时间将缩短至 30 秒。提示通常被视为隐形基础设施，尽管代码、配置和数据库模式都有版本控制，但许多团队对提示的管理却像对待便签一样，缺乏历史记录和变更说明。这种管理方式在单一提示的情况下尚可行，但当多个提示相互依赖时，问题便凸显出来。
提示变更日志：为何我对每个发布的提示进行版本控制
出处: The Prompt Changelog: Why I Version-Control Every Prompt I Ship
发布: 2026年3月29日
📄 English Summary
The Prompt Changelog: Why I Version-Control Every Prompt I Ship
A single word change in a prompt, from 'list' to 'enumerate,' disrupted a workflow that had been functioning well for three weeks, causing downstream JSON parser issues. It took 40 minutes to identify the change, which could have been resolved in 30 seconds with a changelog. Prompts are often treated as invisible infrastructure, lacking version control like code, configurations, and database schemas. This approach works for isolated prompts but fails when multiple prompts depend on each other, highlighting the need for better management and tracking.