Skip to main content

Overview

Shipstar connects to your GitHub repositories, analyzes your commits, and uses AI to generate marketing content that focuses on what matters to your users — not implementation details.
All content generation happens asynchronously. You trigger a generation request, and Shipstar processes it in the background.

The Pipeline

1

Connect & Track

Connect your GitHub account via OAuth and select which repositories to track. Shipstar monitors commits across all your tracked repos.
2

Analyze Commits

When you trigger content generation, Shipstar fetches commits from all active tracked repositories for the specified date range (default: last 7 days). Each commit’s message, author, date, and repository are collected.
3

Generate Content

The commits are passed to Claude along with a specialized prompt for the content type you requested. The AI filters out internal noise (dependency bumps, CI fixes, refactors) and focuses on user-facing changes.
4

Review & Edit

Generated content is saved to your project. You can review, edit, and refine it in the dashboard or via the API before publishing.
5

Publish & Distribute

Publish content to get a public URL with an RSS feed. You can also push directly to Slack channels or Intercom for KB articles.

Content Generation

How Commits Become Content

Shipstar doesn’t just summarize your git log. Each content type has a specialized prompt that instructs the AI to:
  • Focus on the user perspective — describe what changed in terms of benefits, not implementation
  • Filter out noise — skip internal refactors, dependency updates, CI/CD changes, and code cleanup
  • Match the format — follow the specific structure and tone for each content type (professional for LinkedIn, concise for Twitter, detailed for blog posts)
  • Never mention tools or AI — the output reads as if written by your team

Content Types

Product Update

Weekly summary of what shipped. Markdown format covering the highlights across all tracked repos.

Feature Blog

SEO-optimized feature announcement (1200-1800 words). Deep dive into the most significant changes with a narrative arc.

Blog Post

General blog post (600-1000 words). Concise coverage of recent development activity.

LinkedIn Post

Professional social post (150-300 words). Polished and engaging, ready to share.

Twitter Thread

3-5 tweet thread. Each tweet stays under 280 characters. Designed for engagement.

Feature Page

Structured JSON with hero section, benefits, how-it-works steps, and CTA. Ready to render on your marketing site.

KB Articles

Categorized help center articles in JSON format. Multiple articles per generation, organized by topic.

Changelog

Structured JSON changelog with categorized entries (new features, improvements, fixes). Each entry has a title and description.

Release Notes Email

Email-formatted release notes with subject line, introduction, structured notes, and closing. Ready to send to subscribers.

Scheduling

Shipstar supports automated content generation on a schedule using calendar events.

Recurring Events

Set up recurring calendar events to automatically generate content on a cadence:
  • Weekly changelog every Friday
  • Monthly blog post on the 1st
  • Bi-weekly product update for stakeholders
Events follow the RFC 5545 RRULE standard, so you can configure any recurrence pattern. Each event triggers the specified content type and can be set to auto-publish.

Publishing & Distribution

Public URLs

When you publish content, Shipstar generates a unique public URL. Published content is accessible without authentication:
  • Changelogs: https://api.shipstar.ai/api/v1/changelog/{slug}
  • Blog Posts: https://api.shipstar.ai/api/v1/blog/{slug}
  • KB Articles: https://api.shipstar.ai/api/v1/kb/{slug}

RSS Feeds

Every published changelog and blog post includes an RSS feed, so your users can subscribe to updates:
  • https://api.shipstar.ai/api/v1/changelog/{slug}/feed
  • https://api.shipstar.ai/api/v1/blog/{slug}/feed
  • https://api.shipstar.ai/api/v1/blogs/feed (all blog posts)

Integrations

Push content directly to the tools your team already uses:
DestinationContent TypesHow
SlackAll typesPublish to any connected Slack channel
IntercomKB ArticlesSync help articles directly to your Intercom help center

Next Steps

Quickstart

Generate your first piece of content in under 5 minutes

API Reference

Explore the full API documentation