Weekly engineering digest
What shipped, what's stuck and what broke, in one message for the team.
Engineering · Software · On a schedule · Updated
Slack
Linear
Jira
GitHubHow do you write a weekly engineering update?
To write a weekly engineering update, set a Loop in Maito for Friday afternoon. It reads merged pull requests and tickets in Linear, Jira or GitHub, lists what shipped, finds pull requests blocked for days, adds incidents from the week, and posts one message in your engineering channel.
How it's done today
Leads collect status in meetings.
What Maito does
- Read merged PRs, open PRs and incidents
- Summarize shipped, blocked and broken
Example
Loop run: Friday 4:00 PM · Engineering digest
Engineering digest, week of Oct 12. Shipped: 14 pull requests merged. The biggest: CSV export (#871), faster search (#869), and the date picker fix (#903). Linear: 9 tickets closed, 6 opened. Blocked: 3 pull requests waiting over 3 days. • #885 Rate limits (4 days), review from Priya • #889 Billing queue (3 days), draft • #880 Audit log export (6 days), merge conflict Broke: 1 incident. Checkout was down 55 minutes on Tuesday, resolved by rolling back 4.12. Catch: LIN-377 has been In Progress for 19 days with no commits or comments. It may be stuck or forgotten. From merged and open pull requests and Linear.
@Maito what's holding up #885?
Priya was asked on Oct 13 and hasn't reviewed. Checks pass. Sam left 2 unresolved comments about the burst limit on Oct 14.
Maito (4:00 PM):
Engineering digest, week of Oct 12.
Shipped: 14 pull requests merged. The biggest: CSV export (#871), faster search (#869), and the date picker fix (#903). Linear: 9 tickets closed, 6 opened.
Blocked: 3 pull requests waiting over 3 days.
• #885 Rate limits (4 days), review from Priya
• #889 Billing queue (3 days), draft
• #880 Audit log export (6 days), merge conflict
Broke: 1 incident. Checkout was down 55 minutes on Tuesday, resolved by rolling back 4.12.
Catch: LIN-377 has been In Progress for 19 days with no commits or comments. It may be stuck or forgotten.
From merged and open pull requests and Linear.
Alex (4:09 PM):
what's holding up #885?
Maito (4:10 PM):
Priya was asked on Oct 13 and hasn't reviewed. Checks pass. Sam left 2 unresolved comments about the burst limit on Oct 14.
How to set it up
- Ask your agent
“Every Friday at 4, post the engineering digest in #eng: what shipped, which pull requests are blocked, and what broke. Use our pull requests and Linear.”
- Connect issue tracker
- Linear
- Jira
- GitHub
Not connected yet? Your agent sends you a link to sign in.
What it won't do
The digest is only as complete as your tickets and pull requests. Work that never reached the tracker will not appear in it.
Questions
Linear, Jira or GitHub, whichever your team connected, plus the repository's pull requests.
Yes. Tell Maito in Slack what to add or drop, and it keeps that format for later weeks.
Yes, on the schedule you set, in the channel you chose. You can ask it to post a draft first instead.