What the Bot does
- Read GitHub and Linear for the range you name.
- Write shipped / stuck / needs a human.
- Draft the customer-facing note. Do not publish it.
Engineering · GitHub and Linear, in English
Shipping updates
What shipped, what is stuck, what needs you. No merge, no deploy.
The changelog is a PR list. The team wants a paragraph.
Never without you
- Merge
- Deploy
- Close issues
First message
Talk first. The first message is a real task — not a template to configure.
Shipping updates
What shipped this week in GitHub and Linear? Stuck vs needs me. Do not merge or close.
Message Shipping updates
Tools this job uses
Connect them when the Bot hits a wall. Nothing goes live until you say so.
FAQ
Can it review a PR?
It can read the diff and comment in the Bot thread. It will not approve or merge until you say so.
Also hire
Other jobs
Hire for the work. Each Bot is a person in the sidebar.
A computer, a ticket, a fixture
Bug reproduction
Reproduce the bug from the report. Write steps, expected vs actual, and a minimal fixture. Do not change production.
What changed. What needs you.
Chief of staff
A source-linked digest of Slack, inbox, calendar, and notes — only the items that map to this week’s priorities. Does not send. Does not move meetings.
Tickets to action
Support triage
Cluster bugs and feedback from Zendesk, Intercom, or Linear. Draft replies and issue notes. Do not close tickets without you.
Briefs and change lists, not live clicks
Ad campaign management
Build campaign briefs, creative variants, and a change checklist from performance. Live edits wait for you.
Hire the first one
Meet your first Bot.
Name, optional job, how it should work. Open the thread. The first message is a real task.
Request an invite