Step 1
Write the change with your own agent
Use your editor or terminal and the coding agent you already have. Nothing changes in how you write code.
Agent to PR
Let SHIP review and test your coding agent's pull request
Write the change with your coding agent and open the pull request. One command sends it to SHIP, which reviews it, tests it and gives it back ready to merge.
- For
- Developers who write code with a coding agent in their editor or terminal.
- Instead of
- A pull request you must push through CI, review and testing yourself.
Answer 4 questions, then create your account. Your first missions are free.
ship delegate prHow it works
Finish the change, then send it to SHIP
Step 2
Open the pull request and send it
Run ship delegate pr on the branch, or ask your agent to run it. If the GitHub CLI is installed, it finds the pull request from the branch. If not, pass --pr.
Step 3
Merge what comes back
Your CI runs, the Reviewer reads the diff, and the Tester tests the change on a preview your own pipeline deploys. The pull request comes back with the review, the test result and the proof.
Capabilities
Change one mission and leave the project as it is
Pick a different model for one review
Pass --harness or --model to run this mission's Reviewer on another agent or model, or its Tester with --at qa. Your ship.yml stays as it is.
Add a security check for this branch only
Pass --prompt-file to give the Reviewer extra instructions for this mission, such as a security check. Add --prompt-mode extend to keep your repository's own review rules too.
Send it before CI passes
If CI fails when you send the pull request, the agents fix the failure first. Then they review and test the change.
Answer the Reviewer from your terminal
Send your answer with ship instruct, and the Builder goes back to the open pull request with it.
Run it from CI or a script
Every command takes --json, and a token tied to one project has only the scopes the script needs.
FAQ
Frequently asked questions
Do I need a tracker or a ticket?
No. ship delegate pr creates the mission from the pull request and uses its title. With no tracker, the mission lives in the console, and with Linear or GitHub Issues, SHIP files the issue for you.
Can my coding agent send the pull request itself?
Yes. Say set up https://letsship.ai/SKILL.md to your coding agent once, and it installs the CLI and learns when to run ship delegate pr. You create the API token it asks for, because an agent cannot create its own.
Does SHIP push to my branch or open pull requests for me?
You open the pull request, and SHIP does not open a second one. When CI, the review or the test finds something to fix, the Builder pushes the fix to the same branch.
What does a mission cost?
A mission uses one SHIP credit for up to 3 agent-hours, and one more credit for each further 3 agent-hours or part of them. Your own provider bills model usage at your own rates.
Do I need a preview environment?
No. If ship.yml declares a preview, your own pipeline deploys it and the Tester tests the change there. Without one, SHIP skips the deploy step, and the Tester runs the change in its sandbox.
Can SHIP only test a pull request that is already reviewed?
Yes. ship delegate pr --at qa sends a pull request that is already reviewed straight to the Tester. Add --model or --harness to choose what the Tester runs on.
Try it on your open pull request
Connect your repository, install the CLI, and run ship delegate pr on your branch.
Start your first mission
Answer 4 questions, then create your account. Your first missions are free.