Grokbot TemplatesGrokbot Templates
すべてのユースケース

エンジニアリング

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.

共有

困っていたこと

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.

インストールまたは作成するもの

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.

ボット

  • 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.

プラグイン

  • GitHub

    任意

ファイル

  • A verification skill and feature map the fuzz agents follow (she suggests building one with pstack).

ルーティン

  • 初回の実行では使いません。まず手動で1回通して確認してください。

プロンプト

これはヒントであり、貼り付けられるシステムプロンプトではありません。作者はプロンプトを公開していません。初回の手順に従ってください。

初回実行

  1. 1Read https://x.com/poteto/status/2107527180263829827 (credit @poteto).
  2. 2Create two Team Bots — a release manager and an engineer — and add both to one release channel in Slack.
  3. 3Write (or build with pstack) a verification skill that says how to run your app and what “working” looks like.
  4. 4Tell the release bot you want a cut: it should DM contributors with their PR links and collect blockers.
  5. 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.

承認フェンス

The bots prepare and test; a human still decides whether a fix is cherry-picked into a patch release and when anything ships.

調整ポイント

Split the job: one bot owns the release, one owns the fixes, and a verification skill is what makes the swarm worth trusting.

出典

lauren @poteto · 元の投稿

xAI とは提携していません。このプロンプトは当サイトが書いたものではありません。第三者テンプレートの規約も適用されます。

テンプレートを見る

チーム設計図を見る

Pro パック

アイデアだけでなく、完全な構成が必要ですか？

Pro パックには、人気ユースケースのジョブ本文、プロンプト、スケジュール、落とし穴が入っています。

Pro を見る