How I Auto-Generate Weekly Dev Reports from GitHub + Notion
45 minutes every Friday, down to 3.
I used to manually write dev reports: what got merged, what's still open, what's blocked. Now AI pulls commits from GitHub, cross-references with the Notion task board, and drafts the report in Google Docs.
What You'll Learn
- A prompt that pulls from 3 sources (GitHub + Notion + Docs) at once
- Why cross-referencing catches dropped tasks
- Filtering out 50% of noise from merge commits and CI
The Friday Prompt
You can copy this directly:
Pull the last 7 days of commits from my GitHub repo [owner/repo]. Skip merge commits and anything starting with 'ci:' or 'chore:'. Also get all open issues. Then check Notion for any tasks marked "in progress" or "blocked." Write a weekly dev report in Google Docs with three sections: (1) Completed this week — list merged PRs and commits grouped by feature (2) In Progress — open issues + Notion tasks in progress (3) Blocked — anything marked blocked with the reason why. Flag any Notion task marked 'in progress' that has no related commits in the past 7 days.
AI pulls from three sources, cross-references, and writes a structured report. I review, add context where needed, and send.
The Part Most People Miss
💡 Cross-referencing catches dropped tasks. The real value isn't the commit list — it's the gap analysis. If Notion says a task is "in progress" but there are zero related commits this week, something's wrong. That's why the prompt says "Flag any Notion task marked 'in progress' that has no related commits."
💡 Group commits by feature, not by date. Chronological listing gives you a wall of "fix typo" and "merge branch" noise. Grouping by feature area gives you "auth module: added token refresh" and "Drive adapter: added delete" — one glance tells you what happened.
💡 Filter out the noise upfront. About 50% of commits in an active repo are merge commits or CI-triggered changes. Adding "Skip merge commits and ci:/chore: prefixes" cuts your report from 40 items to 15 meaningful ones.
Where It Gets Tricky
⚠️ AI can't distinguish meaningful from trivial commits. A commit that says "update README" could be a minor typo fix or a major documentation overhaul. AI treats them the same. The real fix is writing better commit messages (team discipline, not an AI problem).
⚠️ GitHub API returns max 30 commits per page by default. If your team had a productive week with 50+ commits, AI only sees the first 30. Specify per_page: 100 in the query, or ask AI to paginate.
Setup
Needs GitHub + Notion + Google Docs — three apps in one workflow.
OctoDock connects all three through one MCP URL. AI pulls commits, checks Notion, and writes the report in Docs — all in one conversation.