weekly-review

Generate markdown weekly progress reports from git history and task files.

3|2|Updated May 28, 2026

Search Tags:#productivity #git history #task tracking #weekly review #markdown report #project recap

Ready to run

npx skills add https://github.com/Clos01/Kenbun-Agent --skill weekly-review-clos01

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: weekly-review
Source: https://github.com/Clos01/Kenbun-Agent/tree/main/core/tools/skills/weekly-review
Command: npx skills add https://github.com/Clos01/Kenbun-Agent --skill weekly-review-clos01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual effort of gathering weekly progress updates by consolidating completed work, pending tasks, and upcoming priorities into a structured recap.

Core Features & Use Cases

Weekly Activity Summaries: Reviews recent git history and organizes completed work from the past week.
Task Tracking Recaps: Aggregates open items from AG_TASKS.md to highlight remaining work and priorities.
Use Case: Use this Skill at the end of a work week to generate a markdown report showing accomplishments, unresolved tasks, and next week's focus areas.

Quick Start

Use the weekly-review skill to create a markdown recap of my completed work, open tasks, and priorities for next week.

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 progress report from git history?▼

Generate a weekly progress report by analyzing recent git history and aggregating open tasks from AG_TASKS.md. The tool collects completed commits and outstanding items to produce a structured markdown report summarizing project activity.

Can I automatically track outstanding tasks for a software project retrospective?▼

Yes, task tracking recaps are generated by aggregating open items from AG_TASKS.md. This highlights remaining work and priorities, providing a clear list of outstanding tasks for software project retrospectives and team updates.

What's the best way to summarize weekly development activity for a team update?▼

Summarize weekly development activity by collecting completed work from git history and pending tasks into a single markdown recap. This consolidates project activity into a structured report suitable for team updates and personal productivity reviews.

Do I need a specific task tracking file to generate a markdown project recap?▼

Yes, an AG_TASKS.md file is required to aggregate open items and highlight remaining priorities. The markdown project recap combines this task tracking data with git history analysis to show accomplishments and next week's focus areas.

When do I need a markdown report for project retrospectives?▼

A markdown report for project retrospectives is needed at the end of a work week to review accomplishments, unresolved tasks, and upcoming priorities. It removes manual effort by consolidating git activity and task tracking into a structured recap.

Does weekly review work with existing repository activity for personal productivity reviews?▼

Yes, weekly review works with existing repository activity by analyzing recent git history. It organizes completed work from the past week to support personal productivity reviews and generate a markdown report of project progress.