weekly-report

Name: weekly-report
Availability: InStock
Author: Adonis0123

Aggregate Git commits across multiple repositories into a Markdown weekly report.

2|Updated Feb 19, 2026

Search Tags:#git #markdown #multi-repo #commit-history #weekly-report #report-generation

Ready to run

npx skills add https://github.com/Adonis0123/adonis-skills --skill weekly-report-adonis0123

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: weekly-report
Source: https://github.com/Adonis0123/adonis-skills/tree/main/.agents/skills/weekly-report
Command: npx skills add https://github.com/Adonis0123/adonis-skills --skill weekly-report-adonis0123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual weekly status reporting across multiple repositories is time-consuming and error-prone. This skill automatically aggregates commit history to produce clear, project-scoped summaries.

Core Features & Use Cases

Consolidates commits across multiple repositories into a single weekly report.
Groups changes by project and filters out trivial commits to highlight meaningful work.
Outputs Markdown reports stored locally for easy sharing and archival.

Quick Start

Run the weekly-report skill in the root of any Git project directory to generate a structured weekly summary.

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 report from Git commit history across multiple repositories?▼

You can generate a multi-repo weekly report by running the skill in a Git project root, which aggregates commits across all refs, filters trivial commits, groups items by project, and outputs a formatted Markdown file.

What is the best way to consolidate Git commits for sprint reviews and management updates?▼

The best way to consolidate Git commits for sprint reviews is to aggregate multi-repo commit history into project-scoped summaries, filter trivial commits to highlight meaningful work, and merge related items into a formatted Markdown report.

Can I specify a time range when aggregating commits for a multi-repo weekly report?▼

Yes, you can use optional time-range support to filter and read commit history across all refs within specific dates, ensuring the multi-repo weekly report only aggregates commits from your defined time window.

Does the weekly report generation process filter out trivial commits automatically?▼

Yes, weekly report generation automatically filters trivial commits by reading history across multiple repositories, grouping changes by project, and merging related items to highlight meaningful work in the final Markdown output.

What format are the generated weekly status reports outputted in for sharing and archival?▼

Generated weekly status reports are outputted in Markdown format and stored locally, providing an easily shareable and archivable file that merges related items grouped by project from aggregated Git commit history.