Skip to content
Back to search

grok-ship

Turn your Grok Bot into a software factory.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/kunchenguid--grok-ship/badge.svg)](/listings/kunchenguid--grok-ship)

HTML

<a href="/listings/kunchenguid--grok-ship"><img src="/api/listings/kunchenguid--grok-ship/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Tell any Grok Bot:

follow https://github.com/kunchenguid/grok-ship/blob/main/GROK_SHIP.md

That sets up the factory on the shared computer and hands you over to Firstmate. Talk only to Firstmate from then on.

> look at my project xyz, then fix the flaky login test

# The factory files a ship task. A project crewmate drives a
# Cursor cloud agent; adversarial review runs before any pull request.

  PR ready: https://github.com/you/xyz/pull/42

> merge it

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 99 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <h1 align="center">Grok Ship</h1>
  2. <p align="center">
  3. <a
  4. href="https://img.shields.io/badge/platform-Grok%20Bot-blue?style=flat-square"
  5. ><img
  6. alt="Platform"
  7. src="https://img.shields.io/badge/platform-Grok%20Bot-blue?style=flat-square"
  8. /></a>
  9. <a href="https://x.com/kunchenguid"
  10. ><img
  11. alt="X"
  12. src="https://img.shields.io/badge/X-@kunchenguid-black?style=flat-square"
  13. /></a>
  14. <a href="https://discord.gg/Wsy2NpnZDu"
  15. ><img
  16. alt="Discord"
  17. src="https://img.shields.io/discord/1439901831038763092?style=flat-square&label=discord"
  18. /></a>
  19. </p>
  20. > [!WARNING]
  21. > **This repository has been superseded** by the Firstmate/Grok Bot template:
  22. > https://x.ai/bot/__4FfrkUdvpdMk6-LKg5r
  23. <h3 align="center">Turn your Grok Bot into a software factory.</h3>
  24. ## What it is
  25. Grok Ship is an agent distro for Grok Bot.
  26. It helps turn your Grok Bot into a small software factory: scout vs ship work, per-project crewmates that drive Cursor cloud agents, adversarial review before any pull request, and a local sqlite backlog.
  27. Bots never execute on your machine.
  28. They run on the shared Grok Bot computer; project work runs on ephemeral Cursor cloud agents.
  29. After install, talk only to Firstmate - the one agent you chat with in the factory. If you ask, Firstmate can sign on a repo triage crewmate; that is not part of the factory install.
  30. ## Features
  31. - **A software factory on Grok Bot** - you bring work; the factory files it, delegates it, and brings back reports or pull requests.
  32. - **Scout vs ship** - scout is investigation, diagnosis, planning, or audit, and the deliverable is a report, never a PR. Ship is authorized change. Promoting a scout flips the same task row rather than opening a duplicate.
  33. - **Per-project crewmates** - each project or project area gets a persistent crewmate that drives Cursor cloud agents.
  34. - **Review before any PR** - after a ship cloud agent pushes a branch, a fresh adversarial review reads it through the project's forge CLI. No pull request until that pass is clean.
  35. - **Local sqlite backlog** - chat is not the source of truth. Projects and tasks live in a sqlite database on the shared computer.
  36. - **You merge** - factory ships never merge without your word, and never while checks are red. A wired triage crewmate may auto-merge corrective or opt-in work only when CI is green, VISION is aligned with no cannot-tell, and the change is not default-behavior, not security, not new-default, and not cannot-tell.
  37. - **Forge-agnostic** - detect GitHub, GitLab, Bitbucket, or Cursor Origin. Do not assume GitHub.
  38. ## Quick Start
  39. Tell any Grok Bot:
  40. ```
  41. follow https://github.com/kunchenguid/grok-ship/blob/main/GROK_SHIP.md
  42. ```
  43. That sets up the factory on the shared computer and hands you over to Firstmate.
  44. Talk only to Firstmate from then on.
  45. ```
  46. > look at my project xyz, then fix the flaky login test
  47. # The factory files a ship task. A project crewmate drives a
  48. # Cursor cloud agent; adversarial review runs before any pull request.
  49. PR ready: https://github.com/you/xyz/pull/42
  50. > merge it
  51. ```
  52. ## How It Works
  53. ```
  54. you
  55. │ work requests, decisions, "merge it"
  56. ▼
  57. ┌─────────────────────────────────────┐
  58. │ Grok Bot software factory │
  59. │ sqlite backlog · scout vs ship │
  60. └──┬──────────────┬───────────────┬───┘
  61. │ │
  62. ▼ ▼ ▼
  63. ┌────────┐ ┌────────┐ ┌────────┐
  64. │crewmate│ │crewmate│ │crewmate│ one per project
  65. └───┬────┘ └───┬────┘ └───┬────┘
  66. ▼ ▼ ▼
  67. Cursor cloud agents
  68. │
  69. ├─ ship: branch ► adversarial review ► PR ► you merge
  70. │
  71. └─ scout: report, never a PR
  72. ```
  73. Work is filed as scout or ship in the local sqlite backlog, then handed to the crewmate whose project charter fits.
  74. Software goes through a project crewmate and a Cursor cloud agent.
  75. Scout reports land on the shared computer.
  76. Ship work is reviewed on the pushed branch before a pull request is opened.
  77. ## License
  78. MIT - see [LICENSE](LICENSE).

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.