Start the day knowing what moved in the repo
A short brief showing what shipped and what is waiting on a person. Built for an engineering manager reconstructing yesterday from notifications.
GitHub
Slack
4 steps2 integrationsRuns weekdays 8am
Merged work and stalled reviews look the same. What it costs while the work is still done by hand.
- 01Merged work and stalled reviews look the same in a notification list.
- 02The pull request waiting longest is the one nobody notices.
- 03Standup starts with catching up rather than deciding.
- Read merged9 merged · 4 repos
- Read open PRs14 open · oldest waiting 6d
- Build brief9 merged · 14 waiting · 2 blocked
- Post to Slackpost_message · #eng standup
One workflow, four steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01Read what merged since yesterday.GitHub
- 02Read what is open and how long it has waited.GitHub
- 03Assemble a brief split into merged, waiting, and blocked.ModuleX
- 04Post it to the team channel before standup.Slack
The workflow is an editable graph. Reading runs freely; post it to the team channel before standup waits for your opt-in approval until you loosen it. The graph is the receipt.
What moved, before standup. Paste this into ModuleX chat, or hit Use this workflow.
start the day knowing what moved in the repo: read what merged since yesterday; read what is open and how long it has waited; assemble a brief split into merged, waiting, and blocked; post it to the team channel before standup. Ask me before anything is sent or written.
to: composerOr skip the workflow entirely. Ask the assistant in chat and it runs the same job agentically: it picks the right actions, chains them, and reports back. The composer is for when you want it repeatable.
Start the day knowing what moved in the repo. A short brief showing what shipped and what is waiting on a person.
- github · list_pull_requests
- slack · post_message
A short brief showing what shipped and what is waiting on a person.
Where this fits. The tools it runs on, and the teams that run it.
Keep the momentum. Nearby workflows that reuse the accounts you just connected.
Check database health without opening the dashboardA short, regular status that tells you when something moved out of range, and stays quiet otherwise. Built for a small team with no dedicated operations engineer.
Put an external MCP server to workA tool that was not in the catalog, usable in the same place as the 175+ that are. Built for teams with internal tools that no catalog will ever cover.- Get a first-pass review onto the pull requestA first-pass review on the pull request while the author still has the change in their head. Built for a team where pull requests wait a day for anyone to look at them.
About this use case.
It posts one brief to a channel; it does not message individuals.