Ingeniería
Release day with two Team Bots: a release manager and an engineer
Cutting a release means chasing contributors, babysitting the build, and clicking around for bugs.
Qué dolía
Lauren (@poteto) automated her team's release and QA with two Team Bots in a dedicated Slack channel: sandcastle, the release manager, and poteto, the engineer bot. She added that it works because they have a high-quality verification skill, and suggests making your own with pstack. Not affiliated with xAI.
Qué instalar o crear
Say “cut” to the release bot. It DMs every contributor with links to their PRs so they can raise blockers. It kicks off the build, watches it, and starts a fuzz swarm that uses the app like a real user (plus a few random “chaos monkey” clickers). Issues go to the engineer bot, which spins up a Cursor Project to triage and fix the high-priority ones. You decide: cherry-pick and patch, or fix in the next release.
Bots
Release manager (sandcastle)
Collects the release scope from contributors, runs the build, and starts the fuzz swarm.
Engineer bot (poteto)
Owns triage and fixes for high-priority issues through a Cursor Project.
Plugins
GitHub
Opcional
Archivos
A verification skill and feature map the fuzz agents follow (she suggests building one with pstack).
Rutinas
Ninguna en el primer uso. Mira primero una pasada manual.
El prompt
Esto es un consejo, no un prompt de sistema para pegar. El autor no publicó uno. Sigue los pasos del primer uso.
Primer uso
- 1Read https://x.com/poteto/status/2107527180263829827 (credit @poteto).
- 2Create two Team Bots — a release manager and an engineer — and add both to one release channel in Slack.
- 3Write (or build with pstack) a verification skill that says how to run your app and what “working” looks like.
- 4Tell the release bot you want a cut: it should DM contributors with their PR links and collect blockers.
- 5Let it run the build and a small fuzz swarm; send any issue to the engineer bot to fix through a Cursor Project, then you pick patch now or next release.
Valla de aprobación
The bots prepare and test; a human still decides whether a fix is cherry-picked into a patch release and when anything ships.
Qué ajustar
Split the job: one bot owns the release, one owns the fixes, and a verification skill is what makes the swarm worth trusting.
Fuente
lauren @poteto · Publicación original
Sin afiliación con xAI. No escribimos este prompt. Siguen aplicando las condiciones de las plantillas de terceros.
Paquete Pro
¿Quieres la configuración completa, no solo la idea?
Los paquetes Pro te dan el texto de la tarea, los prompts, los horarios y los tropiezos de los casos de uso más populares.