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