weekly-review

Consolidate weekly commit history into a concise status recap.

58|5|Updated Aug 30, 2024
One-click install
npx skills add https://github.com/StudyDrift/lextures --skill weekly-review-studydrift
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weekly-review
Source: https://github.com/StudyDrift/lextures/tree/main/.cursor/skills/weekly-review
Command: npx skills add https://github.com/StudyDrift/lextures --skill weekly-review-studydrift

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly understand progress by synthesizing weekly commit activity into a concise recap that highlights bug fixes, technical debt, and net-new work.

Core Features & Use Cases

  • Automated weekly recap of commits, categorized by bugfix, tech debt, and net-new features.
  • Works across the primary branch and a defined recent window (7–10 days) to provide a compact status update for planning and retros.
  • Use Case: status updates, sprint planning, and retrospective discussions.

Quick Start

Summarize the latest 7–10 days of commits into a 2–5 bullet weekly review.

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 git commit summary for sprint planning?

You can summarize git commits by analyzing the primary branch history over the last 7-10 days, excluding merge commits to produce a 2-5 bullet recap. This is useful for generating status updates and facilitating retrospective discussions.

What is the best way to categorize git commit history for a status recap?

The best way to categorize commit history is by classifying commits into bugfix, tech debt, and net-new features. This method synthesizes recent repository activity into a concise format suitable for executive readability.

Does the weekly commit review exclude merge commits from the recap?

Yes, the weekly commit review excludes merge commits. It requires access to the repository's git history and specifically filters out merge commits to ensure the status recap reflects actual development progress.

Can I use this weekly review for repositories with multiple active branches?

No, this weekly review is designed for repositories using the primary branch. It does not support multiple active branches, focusing only on consolidating the last 7-10 days of commit history from the primary branch into a concise recap.

Why does my weekly commit synthesis only cover the last 7 to 10 days?

The weekly commit synthesis covers a 7-10 day window to ensure the status recap remains concise and relevant for planning. This timeframe captures recent progress while producing a compact 2-5 bullet summary suitable for executive readability.