Slack-Triggered Repro / Escalation Routine
看到需要复现才动手，未经批准不回帖。 Acts only when a thread asks for a reproduction, and does not reply until you approve.
窄事件规则：当 #customer-escalations 出现工单链接 +「needs repro」时，Bot 打开工单、在预发复现、在对话中贴复现包——未经批准不回帖到 Slack。避免「每条新消息」监听。 A narrow event rule: when #customer-escalations has a ticket link + “needs repro,” the Bot opens the ticket, reproduces on staging, and posts the repro pack in the thread — does not reply in Slack without approval. Avoid listening to “every new message.”
为什么推荐Why we recommend it 事件触发设计金标准：窄匹配、审批、失败策略。 Gold standard for event-trigger design: narrow match, approval, failure policy.
先在可撤回、不外发的范围内试跑一遍，确认输出可用，再考虑扩大权限。 Try it first in a reversible, non-outbound scope. Confirm the output, then widen permissions.
这条用法已包含可复用 Skill。跑通安全范围后，立刻把步骤固化下来。 This use already includes a reusable Skill. After the safe pass, lock the steps in.
输出稳定后再打开例行 / 定时。本条已有例行形态，不要一上来就无人值守外发。 Turn on the routine / schedule only after output is stable. This item already has a routine shape — do not start unattended outbound.
