Step 1
Connect a repository
SHIP reads the code and writes an overview, one page per module, and the conventions it finds. The first version comes as a pull request.
SHIP writes a wiki of your architecture, modules and conventions as Markdown in your repository. After a merge, it updates the affected pages in a pull request.
Runs today: Schedule an automation with your own documentation prompt. Each run opens a pull request that updates your docs, on the schedule you set.
Answer 4 questions. SHIP emails you when it opens to you.
Step 1
SHIP reads the code and writes an overview, one page per module, and the conventions it finds. The first version comes as a pull request.
Step 2
Edit the pages, delete what is wrong and merge. Every later change to the wiki goes through review the same way.
Step 3
After a merge, SHIP updates only the pages that merge affected, in a small pull request you approve.
The Planner reads the relevant pages before it plans a change, so each mission starts from what your team agreed.
Each page links to the files it describes, so a reader can check a sentence against the code.
The wiki is Markdown in your repository, and it stays there if you leave SHIP.
Pick the harness and model for the wiki. It runs on your own keys, billed at your own rates.
| Devin | |
|---|---|
| Factory |
|
| SHIP | In early access
|
Not yet. A wiki that updates after every merge is in early access. Today, schedule an automation with your own documentation prompt, and each run opens a pull request that updates your docs on the schedule you set.
SHIP's codebase wiki lives in your own repository as Markdown, in a folder you choose. Anything that renders Markdown can show it.
Devin fits a team that wants a generated wiki that its agent also uses to answer questions about the code, through DeepWiki and Ask Devin. Factory fits a team that wants CI to regenerate AutoWiki pages on each push to the default branch, with an optional sync to GitHub's Wiki. SHIP fits when each change to the wiki should come as a pull request your team reviews before it merges.
Yes. On every mission, the Planner, Reviewer and Tester read your repository's CLAUDE.md, and an AGENTS.md it imports with a bare @AGENTS.md line. A file at .ship/agents/<role>.md adds conventions for one role.
Join early access, and get the first version of your wiki as a pull request.
Answer 4 questions. SHIP emails you when it opens to you.