skills.rest
ZanzyTHEbar
ZanzyTHEbarCOMMUNITY
Explore all skills by this author →
𝕏@ZacariahHeimGitHub

weekly-review

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

3|Updated Apr 8, 2025
Search Tags:#git#productivity#retrospective#commit history#status update#recap#weekly summary
One-click install
npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill weekly-review-zanzythebar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: weekly-review
Source: https://github.com/ZanzyTHEbar/dragonarchy/tree/main/packages/opencode/.config/opencode/skills/weekly-review
Command: npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill weekly-review-zanzythebar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing weekly status updates, retros, or planning summaries from memory is time-consuming and error-prone. This Skill turns your actual git commit history into a concise, executive-readable weekly recap grounded in real work. ## 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, with the exact date range stated. - Use Case: Before a Friday standup or sprint retro, run the Skill to get an accurate recap of what you shipped this week without digging through git log manually. ## Quick Start Ask the assistant to generate my weekly review summarizing my commits from the past week.

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 in a git repository. It reads your configured git user email, collects commits you authored over the last 7-10 days on the primary branch, excludes merges, and produces a short bulleted recap with a classification paragraph.

How to write a weekly status update from commit history?▼

Use this Skill to base your status update on actual commit history rather than memory. It groups your commits into 2-5 concise bullets and classifies the work as bug fixes, tech debt, or net-new functionality for an executive-readable summary.

What happens if my git user email is not configured?▼

The Skill checks for a git user email before collecting commits. If the email is missing, it stops and asks you to set it first, since author-based commit filtering depends on that value.

Does the weekly review include merge commits?▼

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

What time range does the weekly commit summary cover?▼

It covers the last 7-10 days of authored commits on the primary branch context. The exact date range used is always stated in the output so the recap period is unambiguous.

Related Skills

Explore More Software Engineering Skills→
paulbrittainpaulbrittain

weekly-review

Summarize weekly authored commits into categorized highlights by bugfix, tech debt, and net-new work.

Community
Intermediate
Rinzler78Rinzler78
1

bmad-retrospective

Analyze completed epic work and story records to identify recurring issues and prepare follow-up actions.

Community
Advanced
etylsarinetylsarin
59

git-workflow

Enforce feature-branch pull request workflows and prevent direct commits to main.

Community
Intermediate
wwsunwwsun
1

daily-progress

Summarize git commit histories into structured daily or weekly work reports.

Community
Intermediate