weekly-report

Aggregate GitHub commits, PRs, and Claude Code sessions into a weekly Markdown report.

Updated Jan 1, 2012

Search Tags:#automation #templates #analytics #github #claude-code #report #weekly

Ready to run

npx skills add https://github.com/ysk1031/dotfiles --skill weekly-report-ysk1031

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: weekly-report
Source: https://github.com/ysk1031/dotfiles/tree/main/claude/skills/weekly-report
Command: npx skills add https://github.com/ysk1031/dotfiles --skill weekly-report-ysk1031

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

The weekly-report skill aggregates GitHub activity (pull requests, commits, file changes) and Claude Code sessions into a cohesive weekly development review, helping individuals and teams quickly understand progress and focus areas.

Core Features & Use Cases

Aggregates GitHub activity (PRs, commits, additions, deletions, changed files) and Claude Code sessions for the chosen period.
Groups results by repository to provide per-project visibility and easy cross-project comparison.
Generates a ready-to-share Markdown weekly report from a predefined template, defaulting to this week's period with auto-detection of active repos.
Supports reruns with a different period and outputs to a user-specified path for convenient archiving.

Quick Start

Generate a weekly development report for the current week covering GitHub and Claude Code activity.

Frequently Asked Questions about weekly-report

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

FAQPage Schema

How do I generate a weekly development report from GitHub commits and Claude Code sessions?▼

To generate a weekly development report, this skill aggregates your GitHub commits, pull requests, and Claude Code sessions into a concise Markdown file grouped by repository. It formats the activity data using a predefined template and outputs the final report to your specified path.

What is the best way to aggregate GitHub pull requests and Claude Code activity for a weekly review?▼

Aggregating GitHub pull requests and Claude Code activity for a weekly review involves coordinating with an activity-reporter subagent to collect additions, deletions, and changed files. This approach automatically detects active repositories and groups results by project to provide clear cross-project visibility.

Can I generate a development report for a custom lookback period instead of just the current week?▼

Yes, you can generate a development report for a custom lookback period instead of the current week. The skill supports reruns with different time periods, allowing you to specify historical date ranges and output the aggregated Markdown report to a user-specified path for archiving.

Does the weekly report skill group activity data by repository for multiple projects?▼

Yes, the weekly report skill groups activity data by repository to provide per-project visibility. This grouping mechanism applies across multiple GitHub repositories and Claude Code projects, making it easy to compare progress and focus areas across your entire development portfolio.

What format does the automated weekly dev activity report output use?▼

The automated weekly dev activity report outputs in Markdown format according to a predefined template. This ready-to-share Markdown file summarizes your GitHub file changes and Claude Code sessions, making it convenient for archiving or distributing to your team.

Do I need to specify an output path when generating a GitHub and Claude Code activity report?▼

Yes, you need to specify an output path when generating a GitHub and Claude Code activity report. This user-specified path determines where the final Markdown file is saved, ensuring the aggregated weekly development review is conveniently archived for later reference.