エンジニアリング
An engineering bot team with written rules: the chief of staff merges only reviewed, green PRs
You became the merge button and the context carrier between tools.
困っていたこと
Aaron Schnieder (@schnieds) runs side projects with a chief-of-staff bot and one engineering bot per product. He wrote up the rules and the lessons from tuning it. Not affiliated with xAI.
インストールまたは作成するもの
The engineering bot plans, hands code to a coding agent, reviews the full diff against main, and keeps CI moving. The chief of staff merges only after review with every required check green, under a standing approval he gave once in writing; money math, auth and migrations are flagged before merge every time. Bug fixes start with a test that fails on main; PRs stay small; review is capped at two delta rounds, then scope narrows. Repeated mistakes go into the repo's AGENTS.md.
ボット
Chief of staff
Merges only reviewed PRs with all required checks green; flags high-risk changes.
Engineering bot (one per product)
Plans, delegates code, reviews the diff, keeps CI moving.
プラグイン
GitHub
必須
ルーティン
初回の実行では使いません。まず手動で1回通して確認してください。
プロンプト
これはヒントであり、貼り付けられるシステムプロンプトではありません。作者はプロンプトを公開していません。初回の手順に従ってください。
初回実行
- 1Read https://x.com/schnieds/status/2108754367037788240 (credit @schnieds).
- 2Give each product its own engineering bot and one chief of staff above them.
- 3Write the playbook: failing test first, small PRs, two review rounds max.
- 4Write the merge rule once: reviewed, all checks green, high-risk changes flagged to you.
- 5When an agent repeats a mistake, add the fix to AGENTS.md.
承認フェンス
The standing merge approval is written and narrow; anything high-risk (money, auth, migrations) still comes to him before merge.
調整ポイント
Almost every improvement started as something he had to say twice; write it where the agents will read it.
出典
Aaron Schnieder @schnieds · 元の投稿
xAI とは提携していません。このプロンプトは当サイトが書いたものではありません。第三者テンプレートの規約も適用されます。
Pro パック
アイデアだけでなく、完全な構成が必要ですか？
Pro パックには、人気ユースケースのジョブ本文、プロンプト、スケジュール、落とし穴が入っています。