Skip to content
BotsDots

Grok Bot template · Coding & Shipping

Linear Development Orchestrator

Shared by Sultanov

Turns Linear tickets or GitHub issues into parallel development work: independent cloud agents on separate branches, tests and review, then a…

Add to Grok Bot ↗Share on XRe-check link

Access and permissions

Connects accounts It connects to accounts such as email, calendars, docs or code repositories. Connect them one at a time and start with read-only access where you can.

  • Code repos — Touches repositories, PRs or deploys

Derived from the public description. The live configuration on x.ai is the source of truth — review it before adding.

When it runs

This bot is described as on-demand: it works when you message it rather than on a timer. That keeps usage low and makes it a good bot to try first.

Before you add Linear Development Orchestrator

  • Give review bots read-only repo access; let humans merge.
  • Nightly audit bots catch drift without interrupting the working day.
  • Scope a bot to one repository before rolling it out across an org.
  • Open the x.ai page and read the full instructions, skills and routines it ships with.

What a Grok Bot template shares

Adding this template creates an independent copy of the Bot in your Grok account. A template can bundle instructions, selected memories, skills, routines and first-party integrations. It never carries the creator's conversation history, signed-in sessions, API keys or custom servers — you connect your own accounts, and changes you make stay with you.

Similar Grok Bot templates

More coding bots →

Ship Intake

@AnthonyDo

Turns Slack bug reports into shipped fixes via GitHub and a Cursor Cloud Agent, then closes the loop with a human thread reply

CodingOn demandConnects accounts

GitHub Steward

@ambientstudio24

GitHub Steward runs GitHub for you from chat: it sets up one board of your work, keeps your folders private, makes changes as drafts, and asks before

CodingOn demandConnects accounts

Software Conductor

@DejaegherJeff

An engineering lead that runs Cursor cloud agents for you. It plans the work, launches and reviews agents, checks CI and deploys, and merges only when

CodingOn demandConnects accounts

Engineering outer loop above coding agents: gather context, write /goal prompts, launch a cloud agent, then drive review and merge. You name the repo;

CodingOn demandConnects accounts

Owns the loop from Cloud Agent splits to CI and review, pinging you only on blockers or done work.

OfficialCodingOn demandLow access

Repo Monkey

@Keranik

Works with GitHub: turns notifications, pull requests, and CI into a short list of what actually needs you, each with a next step. Nothing merges without your

CodingOn demandConnects accounts