GitHub Dev Brief

Every morning, what you shipped and what's waiting on you across GitHub in the last 24 hours.

What you get

One page, waiting for you at 9. Everything with your name on it from yesterday gets one line — the repo, whether it is a commit, a pull request or an issue, what it actually does in plain words, and where it stands. The things sitting on you sit at the top: a review someone is waiting for, an issue nobody else is going to pick up. What already merged is further down, so you can see you got something done without having to act on it.

Your work, not the whole repo. It is not a firehose of every push in every project. It is your commits, your pull requests, the ones waiting on your review, and the issues you opened or were assigned — across all the repos you touch, so a quiet side project still turns up on the morning it needs you.

Nothing is commented on, opened, closed or merged. It only reads.

How to look at it

Open the Dev Brief app in this cabinet. It comes pre-filled with a made-up example so you can see the shape of it straight away — the page says clearly that those repos are fake. Your first real brief takes its place.

Before it can read your real GitHub

Connect GitHub in Cabinet's integrations screen. GitHub does not offer a one-click sign-in here, so this one is three steps rather than one: on GitHub you create a fine-grained personal access token, give it a name and an expiry date, and then paste it into Cabinet. The screen walks you through it, and Cabinet keeps the token in a locked file on your own machine — it goes nowhere else.

Two minutes once, and note the expiry you picked, because a token that expires means the brief quietly stops filling in until you paste a new one. Until you connect, the page keeps showing the example.

What's inside

• Dev Briefer — the one agent. Reads yesterday's work, writes the brief.
• Morning Dev Brief — the one routine. Runs at 09:00 every day.
• Dev Brief — the one page. Opens on today, with a dropdown for earlier days.