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

做了什么

Staff: /review and /review-bugbot do not attach to cloud agents created by Grok Bot (decided at create time); start a new agent from cursor.com/agents on the same PR branch and include /review-bugbot there.

场景

盯 PR / 仓库

资料完整度

• ✓ 作者与原链接有
• ✓ 做了什么有
• ✓ 来源原文摘录有
• ✓ 截图 / 媒体有
• — 步骤 / 章节来源未提供
• — 提示词 / 配置原文来源未提供
• — 结果 / 数字来源未提供
• ✓ 风险提示有
• ✓ 相关条目有

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

来源原文摘录

Where does the bug appear (feature/product)? Grok Bot Describe the Bug Not sure if this is a bug or a gap, but it feels like I should be able to run Bugbot from cloud agents that Grok Bot creates. Docs say /review and /review-bugbot are available in Cursor 3.7+ and at cursor.com/agents. High effort exists in the Bugbot dashboard. I expected a cloud agent started from Grok Bot to have that same skill, so I could say “review this PR with Bugbot, high effort, fix findings, loop” without a GitHub bugbot run comment and without sitting in the Agents UI / menu. That is not what happens. What I did

展开全文

Repo: private From Grok Bot I launched (and later replied to) several Cursor cloud agents, one per existing PR. Each agent was told, in the launch/follow-up prompt: Stay on the existing PR/branch. Do not open a new PR. …

摘自论坛首帖，照录原文，未翻译。

效果截图

提示词

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

怎么复制

1. 读原文：forum.cursor.com ↗
2. 把原文里的步骤/提示词整理成一条消息交给 Bot
3. 先手动跑一次，再决定频率

风险与限制

• 作者的结果不保证能复现，以原帖为准

用量预估

用金属计算器估一下