Get an evening engineering brief with PR counts, highlights, and team recognition

Every evening, Zero pulls GitHub activity, counts PRs merged per engineer, surfaces commit highlights, and picks an MVP of the day — posted to Slack with no manual work.

Zero conecta:

Why engineering work goes unrecognized without a system

PRs get merged. Engineers do good work. But without a ritual to surface it, the work is invisible — especially to team members who weren't in those review threads. Zero runs a brief every evening: how many PRs did we merge today, who shipped what, and who had the standout contribution. It creates a shared sense of progress and recognition without any overhead.

How to set up the evening engineering brief

@Zero every weekday at 6pm, pull today's merged PRs from vm0-ai/vm0, count per engineer, surface 3 commit highlights, and pick an MVP. Post to #all-vm0.

pruébalo

How Zero gathers activity, computes stats, and writes the brief

Zero pulls GitHub activity for the day

Zero fetches all PRs merged today in the specified repo, along with commit messages and authors.

Zero counts, ranks, and selects highlights

Zero counts PRs per engineer, identifies the top contributor, and selects the 2-3 most impactful commits based on description scope and team impact.

Brief posted to Slack

Zero posts the evening brief to the specified channel — total PRs, per-engineer counts, commit highlights, and MVP recognition with a short description of why they stood out today.

Customize the brief, adjust cadence, or extend to Linear

Add Linear to the brief

Include issues closed alongside PRs merged

@Zero update the evening brief to also include Linear issues closed today per engineer, alongside the GitHub PR counts.

pruébalo

Adjust the MVP criteria

Change how the MVP is selected

@Zero update the MVP selection logic: weight architectural changes more heavily than feature PRs.

pruébalo

Add a weekly rollup on Fridays

Celebrate the full week's output

@Zero on Fridays, post an extended brief: week total, individual PR counts, and the top 3 commits of the week.

pruébalo

Required integrations: Slack and GitHub

Slack

GitHub is required. Zero reads merged PRs and commit data from your repository.

Obligatorio

GitHub

Slack is required. Zero posts the brief to your chosen channel at the scheduled time.

Obligatorio

Linear

Linear is optional. Zero can pull issues closed per engineer to complement the GitHub PR data.

Opcional

Best practices for team engineering briefs

●Post to a channel the whole team sees — #all-vm0 or #engineering — not just a leadership channel. The recognition lands differently when it's public.

●Keep the brief concise: total count, per-engineer, and one standout highlight per MVP. More than 10 lines and people stop reading.

●Run the brief at the same time every day. Predictable cadence builds the habit of checking it.