weekly-review

Generates a weekly summary of authored git commits classified by bugfix, tech debt, and net-new work.

Updated Nov 10, 2013
One-click install
npx skills add https://github.com/bnferguson/dotfiles --skill weekly-review-bnferguson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: weekly-review
Source: https://github.com/bnferguson/dotfiles/tree/main/.agents/skills/weekly-review
Command: npx skills add https://github.com/bnferguson/dotfiles --skill weekly-review-bnferguson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing weekly status updates, retros, or planning notes requires manually digging through git history to remember what you shipped. This Skill automates that by synthesizing your recent authored commits into a concise, executive-readable recap. ## Core Features & Use Cases - Commit Collection: Gathers your authored commits from the last 7-10 days on the primary branch, excluding merge commits. - Work Classification: Groups changes into likely bug fixes, tech debt work, and net-new functionality. - Concise Output: Produces 2-5 summary bullets plus a short classification paragraph. - Use Case: Before a Friday standup or sprint retro, run the Skill to turn a week of commits into a ready-to-paste status update grounded only in actual commit history and diffs. ## Quick Start Ask the assistant to generate a weekly review of my commits from the past week for my status update.

Frequently Asked Questions about weekly-review

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

FAQPage Schema
How do I generate a weekly summary of my git commits?▼

Run the weekly-review Skill, which reads your git user email, collects commits you authored in the last 7-10 days on the primary branch, excludes merges, and produces 2-5 summary bullets plus a classification paragraph.

How to write a status update from git history?▼

Use this Skill to turn commit history into an executive-readable recap. It groups meaningful changes into concise bullets and adds a short paragraph classifying work as bug fixes, tech debt, or net-new functionality.

What happens if my git email is not configured?▼

The Skill checks the repo config for your git user email first. If it is missing, it asks you to set it before proceeding, since author-based commit filtering depends on that email.

Does the weekly review include merge commits?▼

No. Merge commits are explicitly excluded from the collection step so the recap reflects only meaningful authored changes rather than branch integration noise.

What are the limitations of commit-based weekly summaries?▼

The recap is grounded only in commit history and diffs, so work not committed to the primary branch will not appear. Classification into bugfix, tech debt, or net-new is inferred from commit content and may not perfectly match intent.