skills.rest
inernoro
inernoroCOMMUNITY
Explore all skills by this author →
GitHub

weekly-update-summary

Aggregate git history, PRs, and contributor activity into weekly Markdown reports.

2|1|Updated Dec 10, 2025
Search Tags:#automation#documentation#git-history#pr-analysis#weekly-report#team-visibility
One-click install
npx skills add https://github.com/inernoro/prd_agent --skill weekly-update-summary
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: weekly-update-summary
Source: https://github.com/inernoro/prd_agent/tree/main/.claude/skills/weekly-update-summary
Command: npx skills add https://github.com/inernoro/prd_agent --skill weekly-update-summary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool automates the creation of weekly project reports by collecting and analyzing git history, merged PRs, and contributor activity. It turns raw repository activity into a structured narrative that teams can review in one place.

Core Features & Use Cases

  • Aggregates commits, merges, and contributor data from the current week for concise visibility.
  • Analyzes changes, groups them into major themes, and outputs a Chinese-language weekly summary suitable for stakeholders.
  • Saves the final report to doc/report.YYYY-WXX.md for archival and sharing.

Quick Start

Say the trigger words to generate the weekly report and let the tool read the git history to write doc/report.YYYY-WXX.md.

Frequently Asked Questions about weekly-update-summary

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

FAQPage Schema
How do I automate weekly report generation from git history and PRs?▼

You can automate weekly report generation by using trigger words to instruct the tool to read git history and analyze merged PRs and contributor activity. It then outputs a structured Markdown summary for stakeholder updates.

What is the output format for the generated weekly project report?▼

The weekly project report is output as a Markdown file saved directly to doc/report.YYYY-WXX.md. This format allows teams to archive and share contributor activity and major change themes efficiently.

Does the weekly git summary tool require access to the entire repository history?▼

Yes, generating the weekly git summary requires access to the repository's git history. The tool reads raw repository activity including commits and merges to group changes into themes for the report.

Can I use this tool to group repository commits into major themes for demos?▼

Yes, this tool groups repository commits into major themes suitable for demos. It analyzes raw git history and contributor data to create a structured narrative for weekly team reviews and stakeholder updates.

When do I need to generate a Chinese-language weekly summary from git activity?▼

You need a Chinese-language weekly summary from git activity when your stakeholders require localized reporting. This tool analyzes repository changes and outputs the summary in Chinese for team visibility.

Related Skills

Explore More Software Engineering Skills→
26mitch2626mitch26

gstack-openclaw-retro

Analyze Git commit history to generate engineering retrospective reports.

Community
Advanced
i9wa4i9wa4
11

daily-report

Generate daily GitHub activity reports and post them as issues.

Community
Advanced
ChatAndBuildChatAndBuild
1

Automation Triggers

Design and validate CI/CD pipeline triggers with concurrency controls and approval gates.

Official
Advanced
baleen37baleen37
4

generate-status-report

Generate Jira project status reports via JQL with optional Confluence publishing.

Community
Advanced