weekly-review

Generate a weekly summary from repository commit history.

1|Updated Sep 18, 2015

Search Tags:#git #commits #review #engineering #status #summarize #weekly

Ready to run

npx skills add https://github.com/martindzejky/dotfiles --skill weekly-review-martindzejky

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the generation of a concise weekly summary from a project's commit history, giving leadership-ready visibility into what shipped, what was fixed, and what is in progress.

Core Features & Use Cases

Weekly commit synthesis across the main branch suitable for status updates, retrospectives, or planning.
Excludes merge commits to keep the recap focused on substantive changes.
Classifies changes into likely bug fixes, tech debt, and net-new functionality for quick narrative framing.

Quick Start

Ask your AI to generate a concise weekly recap from the last 7-10 days of authored commits on the main branch, formatted as 2-5 bullets plus a short classification.

Frequently Asked Questions about weekly-review

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

FAQPage Schema

How do I summarize git commits for a weekly engineering status report?▼

To summarize git commits for a weekly engineering report, this skill gathers authored commits from the primary branch over the last 7-10 days, excludes merge commits, and groups changes into 2-5 leadership-friendly bullets classifying bug fixes, tech debt, and net-new work.

What is the best way to generate a leadership recap from recent project commits?▼

Generating a leadership recap from recent project commits involves filtering out merge commits and categorizing substantive changes. This skill automates that process by classifying the last week of git history into bug fixes, tech debt, and net-new functionality.

Do I need a configured git user email to generate a weekly commit summary?▼

Yes, a configured git user email is required to generate a weekly commit summary. This skill enforces this guardrail to successfully gather authored commits and exclude automated merges from the primary branch recap.

How does this approach handle merge commits when summarizing engineering status?▼

When summarizing engineering status, this approach automatically excludes merge commits from the recap. This keeps the weekly summary focused strictly on substantive changes like bug fixes and net-new work rather than branch integrations.

Can I use this to classify tech debt and bug fixes from multiple contributors?▼

Yes, you can use this to classify tech debt and bug fixes from multiple contributors. It is specifically designed for software projects with multiple contributors, categorizing their authored commits into a concise narrative for retrospectives or planning.

What limitations exist when summarizing git history for status updates?▼

Limitations when summarizing git history include focusing exclusively on the primary branch for the last 7-10 days. It requires a configured git user email and targets authored commits, meaning unrelated branch activity or longer timeframes are not included in the recap.