给一个仓建编码 bot。它找到 issue,GitHub 连上后真的关了。
仓库里有具体 issue,想看 bot 能不能自己跟完。
它找到对的仓,看过 issue 29,并带说明关掉。
先圈少数核心仓,不要所有仓。Debbie 只打了 playwright movies,它找到了 debs-obrien/playwright-movies-app。
打开 issues,拉出具体那条。她让它看 issue 29,超时测试。
它发现测试已经用 waitForURL,没有 hard wait。
她说连上后再关。它带说明关了 issue。她自己点进 GitHub 核对过。
好在哪:它能找到对的仓,也能真的关 issue。坑在哪:Cursor 里已接的 GitHub,和它电脑上那一套不是一回事,写仓库前要在它那边再接一次。
Create a coding and repos bot. My code lives on GitHub. Start with a mix: a few core repos, not everything. I will point you at a repo by a short name if I cannot remember the exact slug — find the right one from my GitHub. First job: open issues, check stars, and bring up a specific issue I name. Do not close or write until GitHub is signed in on your computer (I will take over for login and 2FA; do not ask me to paste a token in chat). If Cursor already has GitHub linked, use that for cloud agents and skip a second PAT connector unless we need it. Show me what you found before you close anything.
改写自 https://dev.to/debs_obrien/how-to-get-started-with-grok-bot-4f5n
正文按公开帖 / 官方说明改写。没有点赞、阅读或后台数字。打开来源核原文。 关于