weekly-review

Summarize authored commits into a concise weekly recap with classification.

2.6k|204|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/cursor/plugins --skill weekly-review-cursor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weekly-review
Source: https://github.com/cursor/plugins/tree/main/cursor-team-kit/skills/weekly-review
Command: npx skills add https://github.com/cursor/plugins --skill weekly-review-cursor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly teams and stakeholders often struggle to derive a clear view of the past week's shipped work from raw commits. This skill produces a concise weekly synthesis from authored commits, highlighting bug fixes, technical debt, and net-new work to inform status updates and planning.

Core Features & Use Cases

  • Automated weekly recap: analyzes the last 7-10 days of commits on the main branch and excludes merge commits.
  • Concise bullet synthesis: groups meaningful changes into 2-5 bullets for quick absorption.
  • Classification paragraph: adds a brief paragraph covering likely bug fixes, tech debt work, and net-new functionality.
  • Use Case: ideal for weekly status meetings, sprint retros, and planning sessions with leadership.

Quick Start

Generate a 2-5 bullet summary of the current week's commits.

Frequently Asked Questions about weekly-review

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

FAQPage Schema
How do I summarize weekly git commits for a status update?

Summarize weekly git commits by analyzing the last 7-10 days of authored commits on the main branch, excluding merges, to generate a concise recap of 2-5 bullets for status updates and planning.

What is the best way to classify bug fixes and tech debt from recent commits?

Classify bug fixes and tech debt from recent commits by generating a short classification paragraph alongside the weekly recap, categorizing authored work into bug fixes, technical debt, and net-new functionality.

Can I exclude merge commits when generating a weekly code review summary?

Yes, you can exclude merge commits when generating a weekly code review summary. The skill analyzes only authored commits from the main branch over the past 7-10 days, filtering out merge commits for a cleaner recap.

Does the weekly commit recap work without any special git config?

Weekly commit recap requires standard git config to access branch history. The skill includes guardrails about missing git config to ensure authored commits are properly attributed before generating the synthesis bullets and classification paragraph.

Why does my weekly commit summary show fewer commits than expected?

Weekly commit summaries may show fewer commits than expected because the analysis only covers the last 7-10 days of the main branch and intentionally excludes merge commits, focusing solely on authored work for the recap.

Can I use weekly commit analysis for sprint retros and planning sessions?

Yes, weekly commit analysis is ideal for sprint retros and planning sessions. It synthesizes shipped work into 2-5 concise bullets and a classification paragraph, giving teams and leadership a clear view of bug fixes, tech debt, and new features.