weekly-review

Summarize weekly Git commits into categorized bug fix, tech debt, and net-new bullets.

2|Updated Apr 3, 2026

Search Tags:#git #retrospective #commits #reporting #summary #sprint #weekly

Ready to run

npx skills add https://github.com/kscius/KS-Cursor-Orchestrator --skill weekly-review-kscius

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: weekly-review
Source: https://github.com/kscius/KS-Cursor-Orchestrator/tree/main/skills/weekly-review
Command: npx skills add https://github.com/kscius/KS-Cursor-Orchestrator --skill weekly-review-kscius

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill produces a concise weekly synthesis of authored commits, highlighting bug fixes, technical debt, and net-new work for leadership and planning.

Core Features & Use Cases

Automated weekly synthesis: Aggregates commits from the last 7–10 days and classifies them into bug fixes, tech debt, and net-new work.
Executive-ready summaries: Outputs 2–5 concise bullets suitable for status updates and sprint retros.
Use Case: Ideal for weekly sprint reviews and project planning to communicate progress and priorities.

Quick Start

Run weekly-review at the end of the week to generate a 2–5 bullet recap of the last week's commits categorized by bug fixes, 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 summarize weekly git commits for a sprint review?▼

To summarize weekly git commits for a sprint review, this skill analyzes the last 7–10 days of main branch activity, excludes merges, and outputs 2–5 concise bullets categorized by bug fixes, tech debt, and net-new work.

What is the best way to categorize technical debt versus new features in commit history?▼

Categorizing technical debt versus new features in commit history is achieved by analyzing commit messages and diffs to classify changes into bug fixes, tech debt, and net-new work for governance and reporting.

Can I generate an executive-ready summary of recent code changes?▼

You can generate an executive-ready summary of recent code changes by running this tool to produce a concise 2–5 bullet recap highlighting author contributions and categorized work suitable for status updates.

Does this weekly commit reporting tool require access to the main branch?▼

This weekly commit reporting tool requires access to Git metadata and specifically analyzes the last 7–10 days of commits on the main branch to identify author contributions and exclude merge commits.

How are merge commits handled during the weekly retrospective analysis?▼

During the weekly retrospective analysis, merge commits are explicitly excluded from the Git metadata evaluation to ensure the synthesis only reflects actual authored changes like bug fixes and net-new work.