skills.rest
paulbrittain
paulbrittainCOMMUNITY
Explore all skills by this author →
GitHub

weekly-review

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

Updated May 22, 2026
Search Tags:#tech debt#git history#commit analysis#engineering planning#weekly recap#release highlights#bugfix summary
One-click install
npx skills add https://github.com/paulbrittain/claude-team-kit --skill weekly-review-paulbrittain
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: weekly-review
Source: https://github.com/paulbrittain/claude-team-kit/tree/main/skills/weekly-review
Command: npx skills add https://github.com/paulbrittain/claude-team-kit --skill weekly-review-paulbrittain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly summarize what your team shipped over the past week so you can write status updates, support retros, and inform planning without manually reading through commits.

Core Features & Use Cases

  • Weekly synthesis of authored commits: Pulls commits from the last 7–10 days on the primary branch and excludes merge commits to focus on meaningful work.
  • Actionable highlights: Groups changes into 2–5 concise bullets suitable for executive or team updates.
  • Work classification: Adds a short paragraph categorizing likely bug fixes, likely tech debt, and likely net-new functionality based on commit history and diffs.
  • Guardrails for accuracy and readability: Keeps the recap short and only makes claims that are supported by commit history and diffs, asking you to set git email if missing.

Quick Start

Ask the skill to produce a weekly recap for your current repository, grouped into executive-friendly bullets and categorized by bugfix, tech debt, and net-new work.

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 recap from git commit history?▼

You can generate a weekly recap by analyzing authored commits from the last 7–10 days on your primary branch, excluding merge commits. This produces 2–5 concise executive-friendly bullets organized by bugfix, tech debt, and net-new work.

How does commit analysis classify bug fixes versus tech debt?▼

Commit analysis classifies work by examining commit history and diffs to categorize likely bug fixes, tech debt, and net-new functionality. It groups these changes into a short paragraph grounded only in claims supported by the actual diffs.

Can I use commit history to create release highlights for engineering planning?▼

Yes, you can use commit history to create release highlights suitable for engineering planning. The synthesis targets CI-status style reporting, retros, and planning updates by summarizing meaningful work over the past week.

What happens if my git email is missing when summarizing authored commits?▼

If your git email is missing, the recap includes guardrails that ask you to set your git email. Accurate git author attribution is required to correctly identify and synthesize your authored commits.

Do I need to exclude merge commits manually for a weekly synthesis of authored commits?▼

No, you do not need to exclude merge commits manually. The weekly synthesis automatically excludes merge commits on the primary branch to focus solely on meaningful authored work.

Related Skills

Explore More Product & Management Skills→
GenEducationGenEducation

retro

Analyze git commit history to generate weekly engineering retrospectives.

Official
Advanced
StudyDriftStudyDrift
58

weekly-review

Consolidate weekly commit history into a concise status recap.

Official
Intermediate
wollfoowollfoo

context-recovery

Recover project working context by analyzing Git history and file status.

Community
Intermediate
viktorbezdekviktorbezdek
10

git-workflow

Automate Git commit formatting, branch organization, and release note generation.

Community
Advanced