Product Announcement Automation
Yes — Shipstar is a tool that automatically turns code releases into social media announcements, and into the changelog entry, release-notes email, Slack update and announcement banner that go with them. Connect a GitHub repository and a run reads the commits and merged pull requests of a period — seven days by default, or the gap since a schedule's previous run, up to 31 days — and drafts one content type per channel: an X/Twitter thread, a LinkedIn post, a public changelog entry, a release-notes email, a daily or weekly Slack update, or a one-line announcement banner. Every draft waits in a review queue. On approval, X threads are posted to your connected X account, changelog entries publish to your hosted page and embed and go out to changelog subscribers, release-notes emails go to your mailing lists, Slack updates post to the chosen channel, and LinkedIn posts are ready for you to copy. The Free plan is $0 with no card and 1,000 credits a month; an X thread, LinkedIn post or banner costs 25 credits and a changelog entry or release-notes email 100. Solo is $25/month or $240/year for 50,000 credits.
A tool that automatically turns code releases into social media announcements
"Automatically" here means a commit window read on demand or on a schedule — not a hook on every pull request or a trigger on a tag. Shipstar reads what merged in the period, picks the change your customers can actually use, and writes the announcement for the feed rather than copying the changelog. A weekly schedule for an X/Twitter thread and another for a LinkedIn post keeps both feeds moving from the same shipped work; you can scope a run to named repositories and override the project's voice per run. Approved X threads are posted to your connected X account on publish or at the scheduled time. LinkedIn posts are generated for you to copy — direct LinkedIn publishing is coming soon. Daily and weekly product updates can post to a Slack channel. How the posts are written for the feed, and how a hosted pipeline compares with a changelog-to-social CLI, is covered on the Turn Your Changelog into Social Posts page. GitHub is the only source today; GitLab and Bitbucket are coming soon.
Automatically Announce New Features
The features that get announced are usually the ones someone lobbied for — the rest ship into silence. Shipstar removes the lobbying step: because it reads your Git activity, every user-facing change is a candidate for announcement. Small improvements accumulate into a visible drumbeat of progress, and big features get their moment without anyone having to remember to write the post.
Multi-Channel Announcements from One Commit Window
A real announcement lives in five places: the changelog entry, the email to subscribers, the Slack message, the social post, and the banner on your own site. Shipstar drafts each of them from the same commits and pull requests, so the facts agree across channels and each version is written for its medium — a changelog entry documents, a thread earns a stop mid-scroll, a banner is one line with a call to action. Each channel is its own content type with its own draft, review and approval; there is no single button that fans one approval out to five places, which is what keeps an off-message post from going everywhere at once. Schedules keep the channels in step: a weekly changelog, a weekly thread and a monthly banner can all run from the same repository without anyone copying text between them.
Timing Under Your Control
Announcements often need to wait — for the feature flag, the pricing page, the launch day. Shipstar separates generation from publication: drafts are ready when you are, and approved announcements can be scheduled to publish automatically at a specific time. Coordinate a synchronized multi-channel launch, or let routine updates flow out on your default cadence.
A Review Step That Keeps You on Message
Automation drafts; you direct. Every announcement passes through a review queue where you can sharpen the headline, fix the emphasis, or kill the ones not worth announcing. Configure your brand voice once so drafts start close to final. The approval gate means speed without the risk of an off-message announcement going out on its own.
Announce releases from inside your coding agent
The same generation, review, approval and publish steps are exposed over the public API and the Shipstar MCP server (mcp.shipstar.ai, streamable HTTP, OAuth 2.1 with dynamic client registration or an API token), and the Claude Code plugin bundles the endpoint with installable agent skills. An agent that has just merged the release can request the X thread or the changelog entry, read the draft back, approve it and publish it as the last step of its own loop — one tool call per step, no per-IDE recipe or posting script to maintain. The MCP server is listed on the Official MCP Registry and Smithery.
Why teams choose Shipstar
- Every user-facing change becomes an announcement candidate automatically
- Changelog, email, Slack, X and banner drafted from the same commits, each reviewed before it goes out
- Schedule announcements to coordinate launches across channels
- Review gate keeps every announcement on-message
Frequently asked questions
Is there a tool that automatically turns code releases into social media announcements?
Yes — Shipstar. Connect a GitHub repository and a run reads the commits and merged pull requests of a period and drafts the announcement as its own content type: an X/Twitter thread, a LinkedIn post, or the changelog entry, release-notes email, Slack update and announcement banner that go with it. Every draft waits for your review. Approved X threads are posted to your connected X account automatically, on publish or on a schedule; LinkedIn posts are generated for you to copy; Slack carries the daily and weekly product updates. GitHub is the only source today, and the Free plan includes 1,000 credits a month.
How does Shipstar know what to announce?
It reads the commits and merged pull requests in your tracked GitHub repositories and identifies user-facing changes. You decide what's announcement-worthy at review time — drafts you don't approve never publish.
Which channels can announcements go to?
Your hosted changelog page and embeddable widget, changelog email subscribers and mailing lists, Slack channels, X, Intercom, Featurebase, the announcement banner on your own site, and webhooks for custom destinations. LinkedIn posts are generated for you to copy. Each channel is drafted from the same commits and reviewed before it goes out.
Does every merged pull request become an announcement?
No. A run covers a commit window — seven days by default, or the gap since a schedule's previous run — and produces one draft per content type, so a week of merges becomes one thread, one changelog entry or one banner rather than a post per pull request. Refactors, CI changes and internal tooling are left out. When a window holds nothing customer-facing, the single-feature types (X thread, LinkedIn post, banner, feature page) end the run with "nothing to post" and the credits are refunded.
Can I coordinate an announcement across channels at a specific time?
Yes. Approve the announcement and set a publish time — Shipstar publishes automatically when it arrives, across every configured channel at once. Useful for launch days, feature-flag flips, and timed releases.
What about features we don't want announced?
Nothing publishes without approval. Internal refactors are largely filtered out during generation, and anything else you'd rather keep quiet you simply reject or edit out in review.
Explore more
Ship it. Share it. Celebrate it.
Release notes on autopilot.
Free to start. Connect your repo in 30 seconds.
No credit card required · Setup in 30 seconds