Use casesStatus updates

A deploy digest that says what shipped, and who shipped it

Mitra posts a daily deploy digest. At 6pm the agent reads the day's deployments in GitHub and writes one Slack message listing what reached production. Each change names the person who shipped it, reverts go at the top, and nobody scrolls the deploy channel.

Runs: Every day at 6pm
Used by: Engineering

The prompt

At 6pm every day, post one message to #shipped naming what reached production, who shipped it, and any revert.

GitHub

Slack

Build this agent

200 credits to start · no credit card

What the agent actually does.

Read today's deployments
The agent lists every deployment to production since the last digest, with the changes each one carried.
Name who shipped what
Each change is attributed to the person who merged it, so the digest reads as people rather than hashes.
Pull out the reverts
Revert commits and rolled-back deployments are separated out and placed at the top of the message.
Post one message
The digest goes out as a single post, short enough to read on a phone.

Make it yours.

For teams where finding out what went out means scrolling a channel full of bot messages, or asking and waiting. Change any of this by saying so — there is nothing to rewire.

Post per-repository digests to each team's channel instead of one message.
Add a line naming anything merged but undeployed for more than a day.
Say nothing on days when nothing reached production.

Questions, answered.

How do I know what was deployed to production today?

Mitra sends one Slack message at the end of each day with every change that reached production, the person behind each one, and the reverts. The agent reads your GitHub deployments and releases directly, so the digest matches what actually shipped rather than what was planned.

Can a deploy digest tell me when something was rolled back?

Yes. Reverts get their own line, and Mitra puts them at the top of the digest where they get read. The agent spots them from revert commits and rolled-back deployments in GitHub, and on days when nothing was rolled back that line is absent.