← Back to the timeline
poteto
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
poteto
this was all possible because we have a high quality verification skill (https://github.com/cursor/plugins/blob/main/pstack/skills/create-verification-skill/SKILL.md)! create one of your own using pstack https://x.ai/bot/plugin/9717366
Tibo
What if bot goes down
poteto
What if dots weren't mid
poteto
hey im tryna be nice
poteto
Is this why your 28 days are full of nothingburgers
Tibo
Waiting for today’s ship
poteto
yeah i can see why shipping is such a big event for you
Tibo
Lines of code as a measure for productivity?
poteto
Bro is taking “I don’t write code anymore” too literally
poteto
💀 it's a golden potato
Tibo
You really had to sleep on that one
poteto
yo @bot send him a hello world python tutorial
Tibo
So smart. Figured out by itself who needs it
← Back to the timeline