skills.rest
fieldsphere
fieldsphereOFFICIAL
Explore all skills by this author →
GitHub

weekly-review

Summarize weekly commits and categorize changes into debt, bug fixes, and new features.

37|20|Updated Mar 2, 2026
Search Tags:#git#productivity#retrospective#code-review#weekly-review#commit-summarization
One-click install
npx skills add https://github.com/fieldsphere/cursor-team-marketplace-template --skill weekly-review-fieldsphere
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: weekly-review
Source: https://github.com/fieldsphere/cursor-team-marketplace-template/tree/main/plugins/technical-writing/skills/weekly-review
Command: npx skills add https://github.com/fieldsphere/cursor-team-marketplace-template --skill weekly-review-fieldsphere

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a concise, readable synthesis of a developer's weekly work by analyzing recent commits and author activity.

Core Features & Use Cases

  • Commit synthesis: produces a short recap of what was shipped.
  • Change categorization: labels items as debt, bug fixes, or net new functionality.
  • Highlights for retrospectives: compiles 2–5 bullet points suitable for reports.

Quick Start

Run the weekly-review tool to summarize the last 7–10 days of commits authored by you.

Frequently Asked Questions about weekly-review

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

FAQPage Schema
How do I summarize git commits for a weekly sprint review?▼

Weekly commit summarization analyzes your git history from the past 7 to 10 days to generate a concise recap of shipped changes. It categorizes commits into debt, bug fixes, and new features, producing structured bullet points suitable for sprint reviews and progress reporting.

What is the best way to categorize code changes for a personal retrospective?▼

Categorizing code changes for a personal retrospective involves labeling recent git commits as debt, bug fixes, or net new functionality. This synthesis provides 2 to 5 structured highlights that clarify your development progress over the past week.

Can I generate progress reports across multiple git repositories?▼

Yes, you can generate progress reports across multiple git repositories by applying commit analysis workflows to your development activity. This produces a synthetic overview that summarizes your contributions and categorizes changes over the past 10 days.

Does weekly commit summarization work with multi-repository development workflows?▼

Weekly commit summarization is designed to satisfy requirements for multi-repository progress reporting. It analyzes your recent commit activity across various codebases to create a unified, structured output of debt, bug fixes, and new features.

How many days of commit history are analyzed for a weekly review?▼

A weekly review analyzes commit history from the past 7 to 10 days. This timeframe ensures enough development activity is captured to accurately categorize changes and generate actionable insights for your retrospectives.

Related Skills

Explore More Software Engineering Skills→
knishiokaknishioka
7

daily-report-generator

Generate daily and weekly reports from Git commit logs and calendar data.

Community
Intermediate
imclabimclab
1

changelog

Generate internal and player-facing changelogs from git commits and sprint reports.

Official
Intermediate
markus41markus41
18

jira:commit

Create Git commits linked to Jira issues with smart commit syntax.

Community
Intermediate
LeeSandersonLeeSanderson

update-nuget-packages

Automate NuGet package version checks, updates, and release workflows.

Community
Advanced