Cursor SWE Grok Bot Template Setup: 10 Copy-Paste Prompts
10 prompts to install and run Cursor's SWE Grok Bot template: repo scope, triage, cloud agents, PR proof, and the tools you connect after import.

Cursor's SWE Grok Bot template is listed on the marketplace as a software engineer bot that writes code, triages issues, monitors production, and more. The public listing shows no packaged skills or integrations, so after you import it you connect GitHub, cloud agents or other tools yourself, set repo guardrails, and keep merges and production changes with a human. The 10 prompts below turn that install into a usable first week.
The flagship is the SWE bot template prompt for repo triage and cloud agents. Feed it stack, done definition, issue sources, environments, proof rules, connectors, approval gates and ping rules. It returns a job line, after-Add checklist, intake form, triage rubric, handoff template, PR starter, monitoring loop and a worked example.
Official template page: SWE on the Grok Bot Marketplace. Templates are recipes, not clones. Cursor is an Anysphere, Inc. trademark; the Grok and xAI names belong to their owner. PromptDig has no affiliation with either company.
Install and scope
1. After-import connect script
I just added the SWE template. My connectors are [Connectors]. Write a 6-step connect and first-message script that states Environments [Environments] and ApprovalGates [ApprovalGates] without asking for secrets in chat.
2. Repo orientation brief
From this README and folder list [RepoNotes], write a one-page orientation for an SWE bot: stack, test command, where PRs go, and three files it should not touch without asking.
3. Done definition card
Turn [DoneDefinition] into a short card the bot pastes at the top of every task: proof required, environments allowed, and merge owner.
Triage and agents
4. Issue triage table
Triage these issues [IssueList] into ready, needs-design, blocked, or out-of-scope using Environments [Environments]. One line of evidence per row. Invent no ids.
5. Cloud-agent launch prompt
Write a cloud-agent brief for [Task]. Include goal, constraints, tests, proof artifacts, and stop conditions. Ban production credentials.
6. Flaky-test containment
CI failed on [FailureLog]. Propose the smallest local reproduction, what not to retry blindly, and when to ping a human per [PingRules].
Review and quiet ops
7. Risk-first PR review
Review this PR summary [PrSummary]. Lead with break risk, missing tests, and description mismatches, then nits. Do not rubber-stamp.
8. Watch list without noise
Build a weekday watch list for [Services] that only pings on [PingRules]. Include the quiet-day behavior in one sentence.
9. Human approval packet
Package a merge ask for [PrUrlOrNotes]: what changed, proof attached, residual risk, and the exact yes the human must give.
10. Week retrospective
From [WeekNotes], list shipped PRs, false pings, and one process change for the SWE bot next week.
Related on PromptDig
See also the agentic coding task brief prompt, the coding agent system prompt, the Agents hub, and other setup guides in Bot Templates. For template packaging theory, read Templates for Grok Bot.
Not security or employment advice. Humans own merges, secrets, and production.