Each release
Write the changelog
Merged pull requests become release notes people can read.
Engineering docs agentDocs that still match the code.
Point it at a docs space and a repo. It reads recent code changes, finds pages that no longer match and drafts the edits for you to approve.
Your first signup includes $50 in free credits.
On request
Keep engineering docs fresh
- Reads
- Code changes and doc pages
- Grows
- A list of edits
- Lands in
- Confluence
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 ask, compare our Confluence engineering space with pull requests merged in the last month. List pages that are now wrong and draft the changes. Do not edit anything until I say yes.
TulipFarm
I made an agent called Docs keeper and a manual workflow. It reads GitHub and Confluence. Editing a page asks you first. Activate it?
ActivateEdit first
One check, start to finish.
Every run is saved as an agent task you can open, check and rerun.
- Manual
You pick a space and a repo
Run startedStarted - Reads
Pull requests merged in the last month in GitHub
48 pull requests - Reads
Pages in the Confluence space
26 pages - Checks
Does a page describe something that changed?
4 out of date - Asks first
Update the four pages in Confluence
Approved - Updates
Pages in Confluence
4 pagesCompleted
The fix list, before any edit.
Each page comes with the change that made it old and the line to fix.
ConfluenceDocs check · what is out of date
Setup guide
- A pull request changed the install command.
- Fix: replace step 2.
Release process
- The release script was renamed.
- Fix: update the command in step 4.
Looks fine
- 22 pages have no related change.
What gets planted.
Three parts you own and can change at any time.
- Agent
Docs keeper
Compares code changes with pages.
- Skill
Docs style
Your tone and page layout.
- Workflow
On request
Starts when you pick a space and repo.
Uses
- GitHub
- Confluence
Add if you use it
- Google Docs
- Slack
Jira
It reads quietly. It asks before it acts.
Reads without asking
- Merged pull requests
- Pages in the Confluence space
- Your docs style notes
Asks you first
- Editing a Confluence page
- Posting a summary to Slack
It uses your own connections, so it never sees more than you can.
Grow it your way.
Run each month
Move the start to a monthly schedule and get a fix list in your inbox.
Use Google Docs
Point it at a Drive folder of docs instead of Confluence.
Ticket the work
Draft one Jira ticket per page for the owner to fix, after you approve.
Questions, answered.
Will it edit pages by itself?
No. It makes a fix list first. Editing a page asks you first.
How does it match code to pages?
By names, commands and file paths in both. It can miss a link. The list says why it flagged each page.
Can it read private repos?
Only those your own GitHub connection can open.
On request
Draft a PRD from your notes
Turns rough notes and past docs into a first PRD in your template.
On request
Write the how-to for a process
Turns notes and old emails into a clear step-by-step SOP.
Docs and code, back in step.
Public beta, open to everyone. Your first signup includes $50 in free credits.