Weekdays · 10:00
Chase stale pull requests
Finds reviews stuck for days and nudges the right person.
Pull request summary agentKnow what changed before you open it.
Mention the agent in Slack with a pull request link. It reads the diff and replies in the thread with what changed, why and what to check.
Your first signup includes $50 in free credits.
On mention
Summarize a pull request
- Reads
- A pull request and its diff
- Grows
- A plain summary
- Lands in
- A Slack thread
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 someone mentions you with a pull request link, read it. Reply in the thread with what changed, why, and two things a reviewer should check.
TulipFarm
I made an agent called PR summarizer and attached it to your channel. It reads GitHub when mentioned. Replying in the thread asks you first. Activate it?
ActivateEdit first
One mention, start to finish.
Every run is saved as an agent task you can open, check and rerun.
- Mention
Someone shares a PR link in Slack
Run startedStarted - Reads
The pull request, its diff and comments in GitHub
6 files - Writes
Summary and review checklist, using your review skill
1 summary - Asks first
Reply in the Slack thread
Approved - Replies
Message in Slack
DeliveredCompleted
The reply in the thread.
Short on purpose. A reviewer can decide in a minute whether to dive in.
#engineeringPR summarizer APP · 11:14
Summary · Add share links
What changed
- Adds a link button to the report page.
- Adds one table column for link ids.
Why
- The description says users export to share. This removes that step.
Check
- Who can open a link? No test covers expired links.
What gets planted.
Three parts you own and can change at any time.
- Agent
PR summarizer
Reads a pull request and explains it.
- Skill
Review checklist
Your list of things a reviewer should check.
- Workflow
On mention
Starts when someone mentions the agent.
Uses
- GitHub
- Slack
Add if you use it
Jira
Confluence
MCPLinear
It reads quietly. It asks before it acts.
Reads without asking
- The pull request description and diff
- Review comments so far
Asks you first
- Replying in Slack
- Commenting on the pull request
It uses your own connections, so it never sees more than you can.
Grow it your way.
Post on GitHub
Also add the summary as a comment on the pull request, after you approve.
Add your rules
Put your repo rules in the skill, like tests needed for every fix.
Link the ticket
Read the linked Jira ticket and say if the change matches it.
Questions, answered.
Can it see private repos?
Only the ones your own GitHub connection can open. The run uses your access.
Is it a code review?
No. It is a reading aid. It explains the change and points at risk. People review and approve.
Does it reply on its own?
No. Posting in the thread asks you first.
Each release
Write the changelog
Merged pull requests become release notes people can read.
Weekdays · 8:30
Digest the failing builds
Groups the day's CI failures by cause and who should look.
Read less. Review better.
Public beta, open to everyone. Your first signup includes $50 in free credits.