SHIP
ChatGPT pluginAgentic coding for your SDLC
SHIP is your autonomous software team. Assign a Linear, Jira or GitHub issue to SHIP, and its autonomous coding agents plan, build, review and test the change in your own GitHub repository. A mission works toward a pull request. Your CI, an automated code review and a test of its acceptance criteria each gate it.
Hand work to SHIP from the assistant you already use. File a mission from an issue in your tracker, or from a title and a description. Follow the mission through its stages, and read its verdicts, cost and session logs. Send an instruction to the agent that runs next, or leave a note for it. Read the proof that a run produced, such as test traces and screenshots.
SHIP runs agentic development as a headless AI software factory, so no screen has to be in the loop. You operate the whole mission from your coding agent, your AI assistant, your tracker or your terminal. A Planner, a Builder, a Reviewer and a Tester each do one stage of the agentic SDLC. They follow the agentic engineering practices in your repository, such as its agent instructions and skills. Your CI and a preview deploy are gates between the roles, and work that fails a gate goes back to the Builder with the reason.
Schedule maintenance missions, such as a weekly dependency upgrade. Manage the preview environments of your pull requests and the MCP servers that your agents use.
Sign in with OAuth, or send a SHIP personal access token. A token that you bind to one project can reach only the missions of that project.
You need a SHIP account and a connected GitHub repository. Create an account at https://letsship.ai.
- Featured
- No
not on the featured shelf
Movement
From our daily snapshots over the last 30 days.
Rank by placement
Rank in Developer tools
In its category
How this plugin compares with others in the same category. Positions are counted within the category, not across the whole directory.
Developer tools620th of 742 by placement
| # | Plugin | Position | 7d |
|---|---|---|---|
| 618 | #6906 | — | |
| 619 | #6916 | 211places up | |
| 620 | #6930 | — | |
| 621 | #6935 | — | |
| 622 | #6970 | 100places down |
Example prompts
- “Which SHIP projects can you reach, and what stage is each open mission in?”
- “Assign SHIP-412 to SHIP. Tell me when its pull request passes CI, review and tests.”
- “Turn the plan we just wrote into a SHIP mission that starts at the Builder.”
Skills
ship-agent-runs
Use when the user wants to read an agent's log, find why a run failed, follow a run live or stop an agent. It reads and controls the agent runs of SHIP missions, and each run is one agent in its own sandbox. List the runs of a mission or of the organization, and read the status, resource use and cost of one run. Read what the agent did from its log, follow one run live until it ends, and stop one run. For example, the user asks "what did the builder do on SHIP-412", "why did the QA run fail" or "show me the agent log". Also use it when the user says "stop that agent", or to find the run that makes a mission slow or expensive.
ship-delegate
Use when the user wants to hand a plan, a spec or an open pull request to SHIP. It hands work to the SHIP AI agent team from this repository. Delegate a plan or a spec that you wrote, so SHIP builds it. Delegate a branch with an open pull request, so SHIP runs code review and tests on it and makes it ready to merge. For example, the user says "delegate this", "hand this to SHIP", "let SHIP build this", "let SHIP review this" or "ship this spec". Also use it when the user finishes a plan or a change and asks what to do next.
ship-mcp-servers
Use when the user wants the SHIP agents to use an MCP server, or asks which MCP servers the agents can use. It lets the SHIP agents use the MCP servers that this repository declares. Bind a server to agent roles with a credential, approve its tools, start an OAuth sign-in, choose the MCP file or remove a binding. For example, the user says "let the SHIP agents use our GitHub MCP server" or "give the planner Linear access".
ship-missions
Use when the user wants to follow a SHIP mission, check its status, or pass it feedback, review comments or a decision while it runs. It follows, controls and finishes the SHIP missions that you or the user started. List missions, read the state of one, and send it instructions or feedback. Pause, resume, stop, restart, merge or decline a mission, approve a checkpoint or a credit limit, and read its preview, proof and credits. For example, the user asks "what is the status of SHIP-412", "is SHIP done with it" or "tell SHIP to change X". Also use it when the user says "pause that mission" or "merge it", or asks for a change in one line.
ship-sandboxes
Use when the SHIP agents need a runtime or a tool that is not in their sandbox, or a mission waits for an agent slot. It manages the sandboxes that the SHIP agents run in. Add runtimes and tools to a custom sandbox, build it, read its build log and roll it back. Make a sandbox the default of a project, and connect private package registries. Also read how many agents your missions run at the same time. For example, the user says "the agents need Python", "add a JDK to the SHIP sandbox" or "why does my mission wait".
ship-scheduled-tasks
Use when the user wants to schedule a task that SHIP runs every day, week or month, such as a dependency update. It runs SHIP missions on a schedule. Create a scheduled task from a prompt or a template, change its schedule or prompt, or turn it off and on. Run it now, read what its past runs did and cost, and delete it. For example, the user says "every Monday, have SHIP update our dependencies" or "run a flaky test sweep each week". Also use it when the user asks what the last scheduled run did, or which scheduled tasks a project has.
- Categories
- Sign-in
- On Install
- Capabilities
- File a mission from an issue or a description, Follow a mission through plan, build, review and test, Send instructions to the agent that runs next, Read test traces, screenshots and session logs, Schedule maintenance missions
- Availability
- Available
- Version
- 0.13.5
- Keywords
- coding-agents, code-review, agentic-coding, agentic-testing, pull-requests, linear, jira, github-issues, agentic-sdlc, headless, ship, automated-code-review, ai-sdlc, ai-software-factory, headless-software-factory, delegate
- Created
- October 13, 2026
- More info
- Sponsorship
- Promote this plugin