← Back to library

Draft a weekly recap post from your GitHub activity

Yash Kumar Saini, tired of blanking on what he shipped last week, wired a Sunday GitHub Actions job with three agents. It pulls commits, pull requests, issues and reviews through GraphQL, lets Gemini narrate them in first person, then stores a Notion planner page and an unpublished DEV.to draft.

  • OutcomeStart Monday with a ready draft of what you shipped last week, plus a stats page, instead of trying to remember.
  • SetupAn afternoon+
  • LevelAdvanced
  • CreditYash Kumar Saini
View original
Works with
GeminiCustom agentClaude Code

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 24, 2026

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?

  1. Harvest deterministicallyPull the week's activity with a script; no model needed for this part.
  2. Narrate with a modelConvert the collected activity into a first-person post in a chosen tone.
  3. Fallback planKeep a plain template that runs if the model call fails.
  4. Publish as draftsWrite the Notion page and a draft article, never a live post.
  5. 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.

Prompt0 variables
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?
Only in the narrating step; collecting and publishing are plain code.
Does it publish?
It saves a draft; the author edits and clicks publish himself.

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.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminWorkflow✓ AI dry run

Add a merge check for every way coding agents break code

Keep a running list of the specific ways coding agents have damaged your repository, from hollow tests and invented fake responses to deleted files and silenced type errors, and turn each one into an automated gate that blocks the merge, so the same mistake cannot slip through review twice.

Credit: u/alexmarquardt on r/ClaudeCode

An afternoon+
Operations & AdminPrompt✓ AI dry run

Give your agents one shared wiki that only one agent edits

Replace scattered agent memories with a single Markdown wiki in git: every agent reads a short daily brief from it, agents and scripts file sourced notes into an inbox instead of editing pages, one steward agent checks and merges those notes each morning, and private agent memory keeps only personal preferences.

Credit: Siim Tolk

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Keep a shared team wiki that your agents maintain

Give agents a markdown-and-git wiki they read and write, with drafts reviewed before they become team knowledge.

Credit: najmuzzaman on Hacker News

An afternoon+
Operations & AdminRoutine✓ AI dry run

Unused subscription tokens become small PRs to review

Let a scheduled bot check your remaining subscription quota before the weekly reset and use it to open small PRs toward the goals and to-dos you list.

Credit: ariwilson on Hacker News

Under an hour
Operations & AdminWorkflow✓ AI dry run

Get a weekday brief of only the Google Chat you missed

Start each weekday with one short summary of the Google Chat messages you have not read yet, grouped by space with a link to each, while your unread badges stay in place.

Credit: Mete Atamel

Under an hour