daily-work-summary

Collect local git commits and GitHub activity into daily markdown or JSON summaries.

2|Updated Feb 9, 2026

Search Tags:#automation #git #workflow #github #notion #summary #standup

Ready to run

npx skills add https://github.com/SiTaggart/.agents --skill daily-work-summary

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: daily-work-summary
Source: https://github.com/SiTaggart/.agents/tree/main/skills/standup-skill
Command: npx skills add https://github.com/SiTaggart/.agents --skill daily-work-summary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates cross-repo standup summarization by collecting local git commits and GitHub activity for the previous workday, delivering a concise recap for teams.

Core Features & Use Cases

Scans local repositories for commits from the target day across all branches.
Aggregates GitHub activity via the gh CLI (issues, PRs, reviews) to provide a unified daily narrative.
Outputs results in Markdown or JSON suitable for standups, Notion pages, or team dashboards.

Quick Start

Run python3 scripts/daily_summary.py to generate yesterday's work summary across your local repos and GitHub activity.

Frequently Asked Questions about daily-work-summary

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate a daily standup summary from git commits and GitHub activity?▼

Automate a daily standup summary by collecting local git commits and aggregating GitHub activity via the gh CLI to produce a concise recap of the previous workday. The script scans local repositories and fetches issues, PRs, and reviews to generate a unified daily narrative.

Can I generate a cross-repo work recap that includes local git history and Notion activity?▼

Generate a cross-repo work recap that scans local git history across all branches and includes Notion activity when available. This approach aggregates commits and GitHub issues or PRs to provide a comprehensive daily summary across multiple projects.

Does this daily work summary tool require the GitHub CLI to fetch pull requests and issues?▼

The daily work summary tool requires the GitHub CLI to fetch pull requests, issues, and reviews. It applies the gh CLI to aggregate GitHub activity and combine it with local git commits to format results in markdown or JSON.

What is the best way to format cross-repo standup summaries for a team dashboard?▼

Format cross-repo standup summaries for a team dashboard by outputting the aggregated git and GitHub activity in Markdown or JSON. These structured formats are suitable for standups, Notion pages, or team dashboards to deliver a clear daily recap.

How do I run a script to summarize yesterday's GitHub and local git progress across multiple projects?▼

Summarize yesterday's progress by running the daily summary script, which scans local repositories for commits and fetches GitHub data. It aggregates cross-repo activity to output a structured recap of the previous workday.

Are there limitations when scanning local git commits for a previous workday across all branches?▼

Scanning local git commits for a previous workday across all branches relies on having the repositories locally available. The summarization is limited to local git history and GitHub activity fetched via the gh CLI, without remote repository scanning.