weekly-review

Aggregate git activity, breadcrumbs, and memento notes into a weekly Markdown report.

Updated Oct 1, 2024
One-click install
npx skills add https://github.com/einargudnig/dotfiles --skill weekly-review-einargudnig
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weekly-review
Source: https://github.com/einargudnig/dotfiles/tree/main/claude/skills/weekly-review
Command: npx skills add https://github.com/einargudnig/dotfiles --skill weekly-review-einargudnig

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly review that aggregates git activity across all repositories, collects recent session breadcrumbs and memento notes, surfaces stalled work, and outputs a structured weekly status to Obsidian.

Core Features & Use Cases

  • Consolidates cross-repo activity and sessions into a single weekly note for Obsidian.
  • Identifies stalled work and open follow-ups across multiple projects.
  • Provides a ready-to-review Markdown report for weekly planning and reflection.

Quick Start

Run the weekly-review skill to generate the Obsidian weekly status for the past seven days.

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 cross-project weekly status report from git logs and Obsidian notes?

Generating a cross-project weekly status report requires aggregating git logs from ~/work and ~/personal directories alongside Obsidian breadcrumbs and memento notes to produce a structured Markdown summary in Obsidian.

Can I consolidate git activity from multiple repositories into a single Obsidian note?

Consolidating git activity from multiple repositories into a single Obsidian note is supported by scanning cross-repo git logs, combining them with session breadcrumbs, and outputting a unified Markdown weekly review.

What is the best way to track stalled work across multiple git projects for a weekly review?

Tracking stalled work across multiple git projects for a weekly review is done by synthesizing recent git activity and session breadcrumbs to identify open follow-ups and surface stalled work in a consolidated status report.

Does the weekly cross-project status report require specific folder structures for git repositories?

The weekly cross-project status report requires specific folder structures, operating by scanning git logs specifically across the ~/work and ~/personal directories to aggregate repository activity.

How do memento notes and breadcrumbs integrate with git activity in Obsidian?

Memento notes and breadcrumbs integrate with git activity by being read alongside cross-repo git logs, synthesizing session breadcrumbs and notes to provide context for a structured weekly status report.

When should I use an automated weekly review instead of manual cross-repo git log aggregation?

Using an automated weekly review instead of manual cross-repo git log aggregation is ideal when managing multiple repositories, automatically aggregating git activity, surfacing stalled work, and writing a ready-to-review Markdown report to Obsidian.