Daily GitHub Status Brief

For a dev lead or indie dev who wants a standup ready view of the team's PR activity. It shows the overnight merges and the current open PRs grouped by author and age.

GitHub

The grind

Plenty of PRs, not enough context

Here's what doing this by hand looks like today, and why it doesn't scale.

Prepping for standup means clicking through every repo.
PRs waiting on your review get lost in the notification noise.
You cannot tell at a glance what merged overnight.

MewCP collapses all of this into one prompt. Here's what that looks like.

The flow

4 steps · 1 server

Your agent runs it end-to-end

Query the recently merged PRs.

Query the open PRs.

For each open PR, work out its age and its review request status.

Write the brief with the overnight merges by title, author, and repo, and the open PRs grouped into awaiting review, awaiting changes, and stale for more than seven days.

The payoff

Clarity before standup

Every morning you get a one screen brief of what shipped, what is blocked, and what needs your eyes, before the first meeting.

Paste this into Claude, Codex, or any MCP-connected agent. It'll connect your apps and run the task from start to finish.

Run it yourself

Copy the prompt

prompt

Goal: Daily GitHub Status Brief

MCP servers needed (connected through MewCP): GitHub

Steps:
1. Query the recently merged PRs.
2. Query the open PRs.
3. For each open PR, work out its age and its review request status.
4. Write the brief with the overnight merges by title, author, and repo, and the open PRs grouped into awaiting review, awaiting changes, and stale for more than seven days.

Check with me before sending any message or changing data in a connected app.

More recipes

CLSE