When should you use it?
- Standups ask what you did and you cannot recall
- You want to blog regularly about your work
- Your work is mostly visible on GitHub
Not for: Private repos whose details cannot be published; Auto-publishing without a read
What do you need, and what do you get?
You need
- GitHub token with read access
- Notion database
- Blog platform API key
You get
- Notion page with stats tables and the post
- Draft article on your blog platform
How does it work, step by step?
- Harvest deterministicallyPull the week's activity with a script; no model needed for this part.
- Narrate with a modelConvert the collected activity into a first-person post in a chosen tone.
- Fallback planKeep a plain template that runs if the model call fails.
- Publish as draftsWrite the Notion page and a draft article, never a live post.
- Edit and postAdd images or links, then publish yourself.
The prompt
Our own prompt, inspired by Yash Kumar Saini and written to work in Gemini, Custom agent and Claude Code. Values in lime are placeholders.
Here is a JSON summary of my GitHub activity for the past week: commits, pull requests, issues, reviews and languages. Write a 400-word first-person post in a casual tone about what I worked on and why it mattered, grouped by project. Do not mention anything marked private. Use only facts in the JSON. End with one line on what I plan next, written as a placeholder for me to fill.
Inspired by Yash Kumar Saini: Turning Weekly GitHub Activity Into Blog Posts on Notion + DEV.to. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Check that nothing from private repos leaks into a public draft.
- Narration can overstate small changes; trim before posting.
Our take
Reserving the model for narration while harvesting stays deterministic is the right split, and a fallback template covers outages. Drafts rather than live posts keep a person in charge. Pulling the week's commits, pull requests, issues and reviews with a plain script means the facts come from GitHub, not from a model's memory. Gemini only writes the narration, and the fallback template still produces something when that call fails. Saving the result as a Notion page and an unpublished DEV.to draft keeps you in charge of what goes public. The two things to check before posting are leaks and inflation. Make sure nothing from private repositories ends up in a public draft, and trim narration that makes a small fix sound like a launch. Add the images and links yourself. Running it on Sunday, as Yash does, gives you something useful for Monday standups even if you never publish the post. If most of your work happens outside GitHub, the recap will miss it.
Where the time goes back: The weekly recap writes its first draft from records rather than memory.
FAQ
Where is the model used?
Does it publish?
Source and credit
Inspired by Yash Kumar Saini. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- Turning Weekly GitHub Activity Into Blog Posts on Notion + DEV.to
- Creator
- Yash Kumar Saini
- Published on
- DEV Community
- Original date
- Mar 27, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Custom agent
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.