Use casesStatus updates

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

Mitra can post a daily deploy digest: at 6pm an agent reads the day's deployments in GitHub and writes one Slack message listing what reached production, who shipped each change, and anything that was reverted. Nobody has to scroll the deploy channel to find out.

Runs: Every day at 6pm
Used by: Engineering

The prompt

At 6pm every day, look at what was deployed to production in GitHub since the last digest and post one message to #shipped naming each change, the person who shipped it, and any revert that happened today.

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, along 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 commit hashes.
Pull out the reverts
Revert commits and rolled-back deployments are separated from the rest and placed at the top of the message.
Post one message to Slack
The digest goes out as a single post, short enough to read on a phone at the end of the day.

Make it yours.

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

Post per-repository digests to each team's own channel instead of one company-wide message.
Add a line naming anything merged but still undeployed for more than a day.
Stay silent on days when nothing reached production, rather than posting an empty digest.

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. On days when nothing was rolled back, that line is simply absent.