常驻用量

抄作业 / 做成了什么 / Grok Bot

Prime Directive — a two-Bot coding team where only you merge

标题与摘要为原文,未翻译。

做了什么
Playbook and two shared Grok Bot templates, Builder Prime and Gatekeeper Prime, for a coding team in which one Bot builds, the other reviews and nothing merges without the human's approval, with setup and how-it-works guides.
场景
写代码上线
资料完整度
  • 作者与原链接有
  • 做了什么有
  • 来源原文摘录有
  • 截图 / 媒体来源未提供
  • 步骤 / 章节有
  • 提示词 / 配置原文来源未提供
  • 结果 / 数字来源未提供
  • 风险提示有
  • 相关条目有

— 表示来源没有给出,本站不补写。

来源原文摘录
Prime Directive
RongleCat/awesome-grok-bot (GitHub) · 打开原文 ↗

摘自项目 README,照录原文,未翻译。

来源里的步骤 / 要点
  1. Plan (big work only). For a new subsystem, anything security-related, or roughly 400+ changed lines, Builder Prime writes a short plan and Gatekeeper Prime OK…
  2. Build. Builder Prime branches, codes, tests, and opens a PR that says what changed, why, and where any reused ideas came from.
  3. Prove the fix. Every bug fix ships with a test that fails on main and passes on the PR.
  4. Review. Gatekeeper Prime reads the full diff at the head commit, runs the risky paths, and posts a public review with ranked findings and a verdict.
  5. Fix and re-review. Builder Prime pushes fixes to the same branch. Gatekeeper Prime re-reads what actually changed. It never takes "fixed" on faith.
  6. Your call. You get a short note: PR, commit, checks green, one line on why. Say yes and it squash-merges, locked to exactly the commit you approved.
  7. Public reviews, pinned to the commit. Every review goes on the PR itself and names the exact head SHA it covers. If you build in the open, the review should b…
  8. Every fix proves itself. A bug or security fix comes with a regression test that fails on main and passes on the PR. The reviewer runs it against main to

照录来源原文,未翻译。

提示词

来源没有给出可直接复制的提示词原文。

怎么复制
  1. 打开仓库:github.com/smfworks/prime-directive ↗
  2. 读 README,把仓库链接发给你的 Bot,让它按 README 复现
  3. 先在小范围跑通,再加 routine
风险与限制
  • 涉及付款、下单或预订:先让 Bot 只起草,确认后再执行
  • 作者的结果不保证能复现,以原帖为准
用量预估
用金属计算器估一下