poteto@poteto

我刚把我们发版和 QA 流程自动化了！用 Grok Bot 我做了两个 Team Bot：sandcastle，我的发版经理，和 poteto，我的工程师 bot。我把它们加到 Slack 里，建了个新 channel 来管理发版。 先告诉 sandcastle 我要做一次 cut。它会 DM 所有 contributors，附上他们 PR 的链接，让他们知道下个版本有哪些内容，有问题或反对可以直接 DM 回这个 bot。 然后 sandcastle 启动 build，自动盯着它，并启动一个自动化 fuzz swarm。一般是 10+ 个 agent 跑在 Grok 4.7 xhigh 上来运行 build、点来点去像真实用户一样使用它（用我们的 verification skills 和 feature map），其中一些是有引导的，另外几个是 "chaos monkey" 随机乱点看看什么会坏。 发现问题时，我会让它 @ 我的工程师 bot poteto，开一个 Cursor Project 来负责 triage 和修所有 high pri 的问题。看严重程度，我可能会让它 cherry pick 修复到我们的 release branch 然后发一个 patch release，或者如果是已有的问题我也修但放到下个版本里 这又多了一个 Grok Bot 帮我们团队搞定的繁琐任务

i just automated our release and QA process! using Grok Bot i made two Team Bots: sandcastle, my release manager, and poteto, my engineer bot. i added them to Slack and made a new channel for managing releases. first i tell sandcastle that i want to do a cut. it'll DM all the contributors with links to their PRs so they know what goes in the next release and can DM the bot back if they have any blockers or objections. sandcastle then kicks off the build, watches it automatically, and starts up an automated fuzz swarm. usually this is 10+ agents running on Grok 4.7 xhigh to run the build, click around and use it like a real user (using our verification skills and feature map), some are directed while a few are "chaos monkey" clicking things randomly to see what breaks. whenever it finds an issue, i tell it to @ mention my engineer bot poteto, to spin up a Cursor Project to own triaging and fixing all the high pri issues. depending on the severity i may ask it to cherry pick the fix into our release branch and cut a patch release, or if it's a pre-existing issue i still fix it but include in the next release instead that's one more tedious task that Grok Bot now handles for our team