weekly-review

Generates weekly retrospective reports from git history, learnings, and plan status.

5|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/PatriotAi/ai-lab --skill weekly-review-patriotai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: weekly-review
Source: https://github.com/PatriotAi/ai-lab/tree/main/.claude/skills/weekly-review
Command: npx skills add https://github.com/PatriotAi/ai-lab --skill weekly-review-patriotai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Weekly retrospectives often rely on memory and impressions, producing vague summaries and forgotten insights. This Skill grounds the review in facts by pulling the week's git history, new entries in the learnings journal, and plan statuses, then turns them into a concise report and next week's priorities. ## Core Features & Use Cases - Fact-based weekly summary: Collects git log output, docs/learnings.md entries, and docs/PLAN.md phase statuses to build a done/learned/stuck recap. - Next-week prioritization: Produces 3-5 prioritized items (P0 to P2) drawn from the plan and roadmap. - Persistent reporting and memory compounding: Saves reports to docs/reviews/YYYY-MM-DD.md and promotes significant insights into the learnings journal. - Use Case: On Monday morning, ask for a weekly review and receive a dated report summarizing last week's commits and learnings plus five priorities for the coming week, with an option to schedule it recurring. ## Quick Start Ask the assistant to run the weekly review and summarize this week's git activity, learnings, and plan status into a report with next week's priorities.

Frequently Asked Questions about weekly-review

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

FAQPage Schema
How do I run a weekly retrospective with git history?▼

Ask for a weekly review and the Skill gathers facts automatically using git log --since="7 days ago", new learnings entries, and plan statuses. It then produces a done/learned/stuck summary plus next week's priorities saved to docs/reviews.

What data sources does a weekly review report use?▼

The report is built from three factual sources: the last seven days of git commits, new entries in docs/learnings.md, and phase statuses in docs/PLAN.md. It deliberately avoids relying on memory or impressions.

Can I schedule the weekly review to run automatically?▼

Yes, the Skill supports recurring execution through scheduling mechanisms like /loop or send_later, for example every Monday at 09:00. On a one-off run it will suggest setting up such a schedule.

Where are weekly review reports stored?▼

Reports are saved as Markdown files in docs/reviews/ named by date, such as docs/reviews/2026-06-14.md. Ukrainian is the canonical language, with English available when needed.

What happens if nothing was done during the week?▼

An empty week is treated as a valid result rather than skipped. The Skill records the reason for the inactivity in the report so the pattern stays visible in future retrospectives.