yeyo11/shipcast

Ship + broadcast: launch your GitHub projects without writing the same announcement ten times.
You publish a release. Shipcast reads the project's code, not just its README, writes a launch
piece for every channel, and publishes each one once you approve it: the article on your blog in
English and Spanish, canonical copies on dev.to and Hashnode, posts on Bluesky, Mastodon, Telegram
and Discord, an Instagram carousel with its story, a newsletter issue, and ready-to-paste Show HN and
Product Hunt drafts. Then it reads back how each channel did.
> [!NOTE]
> Shipcast is alpha, built for and used by its author: it launched
> claudio v0.9.0 on six channels. It runs on your own machine
> with your own accounts. Installing it for yourself takes some setup today (below); a GitHub Action
> mode and a one-command install are on the roadmap.
## How it works
1. Opt in per repo. A .github/launch.yml turns launches on and sets a mode for each channel:
approval (published when you approve), manual (a draft for you to post), auto or off.
yaml
# .github/launch.yml
enabled: true
brand: personal
publishing:
blog: approval
devto: approval
bluesky: approval
instagram: approval
hackerNews: manual # the Show HN draft
assets:
demo: docs/demo.gif
2. Trigger. Publish a release (the engine polls your public GitHub events, no webhooks), or pick a
repo and a release in the app. A pre-flight check first makes sure there is a release, a valid
launch.yml, a license, a README and the demo.
3. Analyse. Claude reads the repository and separates what is implemented from what is only
planned or claimed by the docs; only the implemented part is presented as working.
4. Generate. One structured content pack per launch: the article in each language, a piece written
for each channel within its limits, the launch image, the Instagram carousel and story, and a cover
in your blog's style when the project has none.
5. Approve. The drafts arrive as a pull request in your launches repo, which is also your blog's
source. Read and edit every piece in the app or on GitHub; approving merges it and publishes. Or
skip the review and publish straight away.
6. Publish and measure. Each channel is published once, never twice; a failure is retried or left
for you to retry. Visits by channel, search, stars and traffic, and each post's numbers end up on
the launch's page. With Telegram connected, you hear when drafts wait and when a launch is out.
You can also write an article in the app, in your own words: Shipcast translates it, writes each
channel's piece and publishes it the same way.
## The app
pnpm app serves Shipcast's web app on a domain of yours reachable only over your
Tailscale network, with its own Let's Encrypt certificate:
Launches: every launch, where it went, what is waiting for you, and its numbers.
Channels: every network, the accounts connected to each (per brand, several per network), what
Shipcast may do with them, a check of each credential, and OAuth for Mastodon and Instagram. Secrets
live in your operating system's keychain.
Launch a repo and Write, with the choice to review first or publish directly.
Sign-in is with GitHub, limited to the logins you allow. See docs/web-app.md.