Every product update becomes a changelog, visual and social post.
What it solves: A product marketing team connected their GitHub repo to Kylon. Every code change becomes a marketing opportunity: auto-summarized changelogs, generated visuals, scheduled social posts.
How it runs
- Watch every code change The agent scans commits, pull requests and releases daily, leaving out refactors and infrastructure work. Who decides: The product marketer confirms what is worth announcing.
- Summarize in plain language Each product-relevant change becomes a plain-language feature description in the morning digest. Who decides: The product marketer checks each summary.
- Draft every format Posters, slide decks, blog drafts and platform-specific social copy are prepared from one summary, in the brand’s style. Who decides: The marketing team approves each piece.
- Publish across channels Approved posts are scheduled for X and LinkedIn with a suggested posting window. Who decides: The product marketer publishes or schedules each post.
Tools it connects
- GitHub: Holds the commits, pull requests and release notes the daily digest is built from.
- X (Twitter) (optional): Carries approved posts to X, published right away or scheduled.
- LinkedIn (optional): Is where approved updates reach the professional audience, published or scheduled.
Set-up prompt
Paste this into Kylon, or start it in one click below.
Set up our code-to-content pipeline in this Room. Take it one step at a time and wait for my OK before you move on.
1. Connect GitHub first, since the first run needs it. Tell me if it still needs connecting. X (Twitter) and LinkedIn can wait until a step uses them.
2. Ask me who is on the marketing team and who approves what gets published, and help me invite them to this Room.
3. Build a Product Updates App with one record per update: the commits, pull requests or release behind it, a plain-language summary, the customer benefit, the formats planned (poster, slides, blog post, social copy), owner, review status and publish date.
4. Scan the last week of commits, pull requests and release notes in GitHub. Leave out internal refactors and infrastructure changes, and show me the product-relevant updates with their summaries before you save them.
5. For the update I pick, draft a blog post, a feature poster and social copy formatted for X and LinkedIn, following our brand guidelines. Hold every post as a draft for a person to publish or schedule, with a suggested posting window.
6. Copy our brand guidelines, what counts as product-relevant and who approves each format into this Room's guideline.
7. After one clean week, offer to turn the morning digest into a daily Automation.
Start with step 1. Once the tools are connected, or I say the rest can wait, ask me for our rules one at a time.