approve_content) creates the articles in the project’s connected Featurebase help center — in the collection the schedule chose, else the Featurebase destination’s default collection — and only then does the content read “published”. A failed delivery (rejected API key, missing collection) keeps the set in review with the error shown in the dashboard.
Featurebase must be connected first: Dashboard → Destinations → Featurebase, with an organization-level API key. list_destinations shows featurebase.connected and the default collection.
Arguments
Seed mode
A normal run documents one commit window. When a help center is empty, passseed: true to document the product as it is: Shipstar reads the tracked repositories’ README and docs folders (up to 24 markdown files) plus the last six months of commits, lists what is already in the Featurebase help center, and asks for an outline of 3–6 collections and up to max_articles articles — skipping titles that already exist. The articles are then written in batches and assembled into one reviewable set, grouped by collection.
On approve, each article is filed under its collection; collections that don’t exist yet are created in the help center. The set-level collection (schedule or default) only applies to articles without one. Seed mode is meant as a one-off; run it again later and it proposes only topics the help center doesn’t cover yet.
Returns
get_content_status, then read the draft with get_content_draft and approve it with approve_content. Once delivered, the content’s metadata carries one entry per created article (article_id, url) under featurebase.articles.
Example prompts
“Write Featurebase help articles for everything we shipped this sprint.”
“Turn the last two weeks of commits into how-to articles for our help center.”
“Our Featurebase help center is empty — seed it from the repo docs, at most 15 articles.”