On mention
Summarize a pull request
Paste a PR link in Slack and get a plain summary and risk list.
Changelog agentRelease notes people can read.
Tell it a release is ready. It reads every pull request merged since the last one and groups them into new, improved and fixed, in plain words.
Your first signup includes $50 in free credits.
Each release
Write the changelog
- Reads
- Merged pull requests
- Grows
- Release notes
- Lands in
- Google Docs
Ask for it once, in plain words.
No flowchart to draw. Describe the job in chat. TulipFarm sets up the agent and its workflow, and shows you both before anything runs.
You
When I say a release is ready, read the pull requests merged since the last release tag. Write release notes in three groups: new, improved, fixed. Keep each line to one sentence.
TulipFarm
I made an agent called Changelog writer and a manual workflow. It reads GitHub. Creating the doc and posting to Slack asks you first. Activate it?
ActivateEdit first
One release, start to finish.
Every run is saved as an agent task you can open, check and rerun.
- Manual
You say the release is ready
Run startedStarted - Reads
Pull requests merged since the last release in GitHub
23 pull requests - Writes
Notes in three groups, using your changelog skill
3 groups - Asks first
Create the notes doc in Google Docs
Approved - Creates
Release notes doc
1 doc - Asks first
Post the link to the releases channel
Approved - Posts
Message in Slack
DeliveredCompleted
The notes, ready to edit.
One sentence per change. Internal work is left out unless you ask for it.
Google DocsRelease notes · next release
New
- You can share a report with one link.
- Reports now have a clearer empty state.
Improved
- The first run is faster to set up.
Fixed
- Dates now show in your time zone.
- Fixed a crash when a file name had a space.
What gets planted.
Three parts you own and can change at any time.
- Agent
Changelog writer
Reads pull requests and writes the notes.
- Skill
Changelog style
Your groups, your tone, what to leave out.
- Workflow
On request
Starts when you say a release is ready.
Uses
- GitHub
- Google Docs
- Slack
Add if you use it
Jira
Confluence
MCPLinear
It reads quietly. It asks before it acts.
Reads without asking
- Pull requests merged since the last release
- Pull request titles and descriptions
- Your previous notes, for tone
Asks you first
- Creating the notes doc
- Posting to Slack
It uses your own connections, so it never sees more than you can.
Grow it your way.
Two versions
Write one set for customers and one longer set for the team.
Tie to tickets
Read linked Jira tickets so each line says why the change matters.
Publish to Confluence
Create the page in Confluence instead of a Google Doc.
Questions, answered.
How does it know what to include?
It reads the pull requests merged since the date or tag you give it. Your skill says what to leave out, such as test-only changes.
Will it publish the notes?
No. It makes a draft. Creating a doc or posting a link asks you first.
Does it change my repository?
No. It only reads pull requests. It does not push code or tags.
Weekdays · 9:00
Check launch readiness
Checks tickets, docs and sign-offs before launch day.
On request
Keep engineering docs fresh
Spots docs that no longer match the code and drafts the fix.
Ship it, then say what shipped.
Public beta, open to everyone. Your first signup includes $50 in free credits.