daily

Compile daily Git activity across repositories into a markdown summary.

2|5|Updated Jan 2, 2026

Search Tags:#automation #git #workflow #reporting #summary #repositories #daily

Ready to run

npx skills add https://github.com/whoabuddy/claude-knowledge --skill daily-whoabuddy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: daily
Source: https://github.com/whoabuddy/claude-knowledge/tree/main/claude-config/skills/daily
Command: npx skills add https://github.com/whoabuddy/claude-knowledge --skill daily-whoabuddy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of a team-friendly daily summary of git activity across multiple repositories, replacing manual reporting chores with a concise, publishable daily brief.

Core Features & Use Cases

Gathers commits across repos under ~/dev and compiles a markdown summary suitable for publishing.
Supports optional capture integration to surface knowledge captures after the summary.
Publishes to a configured logs repo and can include PR and issue activity data.

Quick Start

Run the daily skill to generate today's summary across all tracked repositories.

Frequently Asked Questions about daily

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

FAQPage Schema

How do I generate a daily git activity summary across multiple repositories?▼

To generate a daily git activity summary across multiple repositories, you can run the daily skill. It collects commit data from local repos under your ~/dev directory and compiles them into a cohesive markdown-ready report.

How does automated git workflow reporting compile commits from local repositories?▼

Automated git workflow reporting compiles commits from local repositories by scanning tracked repositories under ~/dev. It aggregates the commit history into a concise markdown summary that can be published directly to a logs repository or shared with teammates.

Does daily reporting work with repositories outside the ~/dev directory?▼

Daily reporting primarily targets repositories located under the ~/dev directory. It applies CLI-driven data collection scripts to gather git activity from these specific local repos to ensure a cohesive daily summary output.

Can I include PR and issue activity in my daily git summary?▼

Yes, you can include PR and issue activity in your daily git summary. The skill supports optional capture integration to surface related knowledge captures and can append pull request and issue activity data to the final markdown report.

What is the best way to publish a daily git summary for a development team?▼

The best way to publish a daily git summary for a development team is using environment-configured publishing targets. The skill outputs a markdown-ready entry point that can be pushed directly to a configured logs repository for team visibility.

Do I need YAML frontmatter to automate daily git workflow reporting?▼

Yes, you need YAML frontmatter to automate daily git workflow reporting. The skill satisfies requirements for a YAML frontmatter-driven entry point, which structures the generated markdown summary before it is published to your logs repository.