Ship Intake
Turns Slack bug reports into shipped fixes via GitHub and a Cursor Cloud Agent, then closes the loop with a human thread reply
By Anthony
From reports in Slack, by email or via support, the bot creates clean tasks with a description, reproduction steps and priority. Nothing gets lost in chat anymore.
Copy the prompt into your Grok bot and replace the parts in square brackets.
Read the bug reports in [channel]. Turn each into a task with: a short title, steps to reproduce, expected and actual behaviour, affected version and a suggested priority. Merge duplicates. Create the tasks as drafts and ask when information is missing.
Make sure no customer data or passwords from the reports end up in the tasks. More on safety
These bots fit best. Open one and add it to Grok in one click.
Turns Slack bug reports into shipped fixes via GitHub and a Cursor Cloud Agent, then closes the loop with a human thread reply
By Anthony
Turns Linear tickets or GitHub issues into parallel development work: independent cloud agents on separate branches, tests and review
By Sultanov
Turns a ticket or screenshot into a staging repro pack another engineer can follow: exact steps, expected vs actual, environment, and evidence
By Gordan
A senior-engineer review and a skeptical second pass in one report. Catches bugs, security holes, and over-engineering — including prototype pollution
By Destin
Triage customer support into Linear: retitle in-app feedback, file factual tickets from Slack/HubSpot, and surface a short diagnosis — never contact
By Stephen
Turns angry bug reports into calm repro cards.
By Andy
27 bots
Turns meeting transcripts into draft backlog items for GitHub or Jira, routing conflicts to a human
Re-certifies production as a real user after each ship and files unique bugs with screenshots; never edits code
by duyet · Open in Grok
Backtests strategy ideas, cleans market data, and reviews research code for bias and bugs
by Avid · Open in Grok
Cursor's software engineer bot: writes code, triages issues, monitors production, and more
by Cursor · Open in Grok
Turns Linear tickets or GitHub issues into parallel development work: independent cloud agents on separate branches, tests and review
Turns a ticket or screenshot into a staging repro pack another engineer can follow: exact steps, expected vs actual, environment, and evidence
by Gordan · Open in Grok
First line of defense on email, Slack, and DMs. Read-only by default — surfaces the ~3 that are both important and urgent. Never answers as you
Plays your web game as a guest for a real session and reports an appeal score, bugs, and top changes with screenshots
by Daniel · Open in Grok
Builds, fixes, and playtests Lua scripts for Tabletop Simulator mods, using GitHub PRs, live injection into TTS, and Workshop publishing
Builds new websites or migrates existing ones onto GitHub and Cloudflare Workers. Walks you from zero accounts through SSH deploy keys, API tokens,
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
A software QA assistant that runs acceptance checks, files structured findings, and watches GitHub or email for new test handoffs
Mystery-shops any ecommerce site end to end and returns a scorecard plus developer-ready bug reports
by Vic · Open in Grok
Burns a GitHub issue list with Orca worktrees on a registered machine
One weekday digest of every PR, issue and comment across your repos
Turns Slack bug reports into shipped fixes via GitHub and a Cursor Cloud Agent, then closes the loop with a human thread reply
A senior-engineer review and a skeptical second pass in one report. Catches bugs, security holes, and over-engineering — including prototype pollution
by Destin · Open in Grok
Triage customer support into Linear: retitle in-app feedback, file factual tickets from Slack/HubSpot, and surface a short diagnosis — never contact
Weekday Slack scans that flag issues and wins, then posts approved company-wide kudos in #general
Turns angry bug reports into calm repro cards.
by Andy · Open in Grok
Team lead for a Godot idle/incremental game project. Coordinates Designer, Developer, Security, Database, and Tester; de-dupes GitHub issues; runs
Oversees a coloring-book factory. On first run it builds the CB team (Architect through Ads miner), then finds instruction bugs, patches them, and walks
by Dave · Open in Grok
Investigates Sentry issues across MCP, CLI, and dashboard with sourced findings
by Sergiy · Open in Grok
Writes the bug report you paste into the right support form
by Fine_Computer_4451 · Open in Grok
The full list could not be loaded right now. Showing the newest bots.
No results. Shorten your search or pick another category.