Morning Brief: PRs Merged and PRs Waiting
For the first ten minutes of the engineering day. DuckyHelper learns GitHub's web API once, then each morning pulls what merged and what's waiting, and reads you the reviews that need you today.
“Give me a brief of PRs merged since yesterday and open PRs waiting on review.”
- 01Learn GitHub's web API, first time onlyBuilt from GitHub's own buttons, forms and requests. Kept on your device and reused next time.
searchPulls(query)getReviews(pr)
- 02Pull everything merged since yesterday
- 03Pull open PRs and who they're waiting on
- 04Flag anything older than a week
- 05Read you the brief, your reviews firstEach morning on a schedule, if you like.
You getThe day starts with a plan. You know what shipped, what's blocked and which reviews are yours. On a schedule, it's ready before you sit down.
A run, drawn from this page · early access on Mac
Nothing to send, so it runs straight through.
Nothing in this job sends a message or pays for anything, so it works through to the end and tells you when it's done. If a step ever would, it's built to stop and ask you first.
If it hits a sign-in, you sign in yourself. It's built not to type your passwords or card numbers.
Do it once. Then let it repeat.
When it's done, it offers to keep doing it: every weekday at 8:00 AM. Each run goes through the API it learned the first time, so it's quick, and it's still built to ask before it sends or pays.
Always-on automations are in early access on Mac.
Before you ask it.
What do I say?
Press fn (Ctrl+Shift+Space on Windows and Linux) and ask out loud, in your own words, like "Give me a brief of PRs merged since yesterday and open PRs waiting on review."
Why is the second time faster?
The first time, it writes small JavaScript tools for GitHub and builds an API from each site's own buttons, forms and requests. After that it calls them directly, so the job runs in one go instead of click by click. It costs less and breaks less.
Will it send anything without me?
It's built to ask first before it sends a message or pays for anything, and to wait for your yes. It may not recognize every send or payment, so keep an eye on tasks that involve messages or money. It's built not to type your passwords or card numbers: you sign in yourself, and it picks up from there.
Why not just do it by hand?
Knowing where the team stands means scrolling PR lists across repos, and stale reviews hide in plain sight.
Can it keep doing this on its own?
Yes. When it's done it offers to make it automatic (every weekday at 8:00 AM). Each run goes the same way and is still built to ask before it sends or pays.
Can I use this today?
Doing jobs in your apps is in early access on Mac. Talking to DuckyHelper, and having it see your screen and draw on it, works today on Mac, Windows and Linux.
- Early access
“Deploy the latest commit on main to production and tell me when it's live.”
Ship the Latest Commit and Watch the Build
See it run
- Early access
“Signups are failing in production. Check the Vercel logs, reproduce it, and open a PR with a fix.”
Debug a Vercel App From Logs to Fix
See it run
- Early access
“Check my Supabase project's health: schema, row security and anything that looks off.”
Check Your Supabase Database Is Healthy
See it run
Do anything
Ask it a question or hand it a job, in any app.
Doing jobs for you is in early access on Mac. Asking works on Mac, Windows and Linux.