Step 1
Pick a template or write a prompt
Start from the dependency upgrades, flaky test sweep or security advisory triage template. Or write your own prompt, with acceptance criteria as a checklist.
Auto maintenance
Keep your codebase current on a schedule
Pick a maintenance template, such as dependency upgrades, and set a schedule. When a run finds work, you get a pull request that passed your CI, a review and a test.
- For
- Teams with a backlog of dependency updates, security fixes and flaky tests.
- Instead of
- Maintenance tickets that wait for a free sprint.
Answer 4 questions, then create your account. Your first missions are free.
Upgrade this project's dependencies and open a single reviewable pull request.How it works
Set a schedule, then review the pull requests
Step 2
Choose when it runs
Run it daily, weekly or monthly, at a time and time zone you set. You can also start a run whenever you want.
Step 3
Review the pull request it opens
Each run files an issue in your tracker, and the agents plan, build, review and test it. You merge the pull request, unless you turned on auto-merge.
Capabilities
Run maintenance while you build features
Skip a run while the last one is open
SHIP skips a scheduled run while the last run's mission is still open, so a weekly automation never opens two pull requests that conflict. This is on by default, and you can turn it off.
Check the log of every run
Every run is logged with its outcome and cost and linked to the mission it started. A skipped run records why SHIP skipped it, so you can see what happened in a run that nobody watched.
Start a run on demand
Start a run from the console, the API or the MCP server. A manual run goes ahead even if the last one is still open, and the log notes that a person started it.
Limit what a run can spend
A mission pauses at 2 credits, or 6 agent-hours, until a member of your team approves more. An unattended run cannot spend more on its own.
Manage automations from the API
Create, list and run automations over the HTTP API or the MCP server, with the same templates as the console.
Evidence
Browse 224 tickets ready to assign or schedule
SHIP publishes 224 use cases in 29 categories, from dependency and runtime upgrades to security patches and flaky tests. Each one is written as a ticket you can assign or turn into an automation.
FAQ
Frequently asked questions
What happens in a week with nothing to upgrade?
The run ends without a code change and says so, because every template says what to report when the run finds nothing to change. You see a clean run in the automation's history instead of an empty pull request.
Can an automation change my CI configuration?
No. SHIP blocks any change under .github/workflows unless a person asks for it, and nobody is there to ask during an unattended run.
What does an automation cost?
Each run is a normal mission, and one credit covers up to 3 agent-hours. Credits come back when a mission fails or needs attention without a pull request. A skipped run starts no mission and uses no credit, and your own provider bills model usage.
Do automations need a tracker?
Yes. Each run files an issue in the project's tracker and assigns it to SHIP, so a project without a tracker can't run automations.
Can automation issues have my tracker labels?
Yes. List labels that already exist in your tracker, and SHIP adds them to every issue the automation files. SHIP never creates labels, so a name your workspace doesn't have is skipped.
Do I still need my dependency bot?
Keep it if it works for you. SHIP's dependency upgrades template puts routine bumps in one pull request, applies the changelog's migration steps and explains any upgrade it could not do safely. That pull request passes your CI, a review and a test before you merge it.
Put your maintenance on a schedule
Pick a template, set a schedule, and review the pull requests it opens.
Start your first mission
Answer 4 questions, then create your account. Your first missions are free.