Weekly Review
- 1.3k installs
- 2.5k repo stars
- Updated August 5, 2026
- cursor/plugins
weekly-review is a Cursor plugin skill that produces a structured weekly synthesis of authored git commits classified into bug fixes, tech debt, and net-new functionality.
About
weekly-review is a Cursor plugin skill that builds executive-readable weekly recaps from git history for status updates, retros, and planning. It reads the current git user email, collects authored commits from the last 7-10 days on the primary branch, excludes merge commits, and groups changes into 2-5 concise bullets plus a classification paragraph covering likely bug fixes, tech debt, and net-new work. Developers reach for weekly-review when they need a factual shipped-work summary without manually scanning a week of commit logs.
- Automated weekly review workflow for Cursor users
- Extracts accomplishments, open questions, and improvement opportunities from recent work
- Generates prioritized action list for the coming week
- Maintains a running weekly review log for long-term pattern recognition
- Hard-gate: always run before planning the next sprint
Weekly Review by the numbers
- 1,300 all-time installs (skills.sh)
- +184 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #408 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/cursor/plugins --skill weekly-reviewAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.3k |
|---|---|
| repo stars | ★ 2.5k |
| Last updated | August 5, 2026 |
| Repository | cursor/plugins ↗ |
How do you summarize weekly git commits for standups?
Run a structured weekly review that surfaces progress, blockers, and next actions across their AI-assisted projects.
Who is it for?
Developers preparing weekly status updates, retros, or planning sessions who want commit-grounded summaries of their own shipped work.
Skip if: Deep code review, sprint estimation, or teams that need cross-author team-wide metrics instead of individual authored commits.
When should I use this skill?
User needs a weekly recap of shipped work for status updates, retros, or planning based on recent git commits.
What you get
Executive-readable weekly recap with 2-5 change bullets and bugfix, tech-debt, and net-new classification paragraph.
- Weekly recap bullets
- Work classification paragraph
By the numbers
- Covers a 7-10 day commit window
- Groups changes into 2-5 concise bullets
Files
Weekly review
Trigger
Need a weekly recap of shipped work for status updates, retros, or planning.
Workflow
1. Determine the current git user email from repo config. 2. Collect authored commits from the last 7-10 days on the primary branch context. 3. Exclude merge commits. 4. Group meaningful changes into 2-5 concise bullets. 5. Add a short classification paragraph covering:
- likely bug fixes
- likely tech debt work
- likely net-new functionality
Guardrails
- Keep the recap short and executive-readable.
- Base claims only on commit history and diffs.
- If git email is missing, ask the user to set it before proceeding.
Output
- 2-5 bullet weekly summary
- Brief classification paragraph (bugfix / tech debt / net-new)
Related skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kHow it compares
Use weekly-review over manual git log scrolling when you need a classified, executive-readable recap of your own recent commits.
FAQ
What time window does weekly-review cover?
The weekly-review skill collects authored commits from the last 7-10 days on the primary branch, excluding merge commits, to build the weekly shipped-work recap.
How does weekly-review classify commits?
The weekly-review skill groups changes into 2-5 bullets and adds a paragraph classifying work as likely bug fixes, tech debt, or net-new functionality based on commit content.