weekly-review

To generate a weekly review, the Skill aggregates local file system changes and git repository activity from the past seven days to synthesize historical workspace activity into a structured Markdown planning report.

An automated weekly reflection consolidates scattered git activity, vault notes, and task progress into a single summary. It works by scanning local git logs and vault directories to identify completed tasks and overdue items.

Yes, weekly review requires access to local git logs and vault directory structures. It needs these dependencies to scan your workspace and synthesize historical activity into a forward-looking plan.

Yes, you can use this to identify stalled projects and overdue items. The Skill facilitates end-of-week reflection by surfacing completed work, open items, and emerging project themes across your local repositories.

The best way to automate end-of-week performance reporting is asking the assistant to scan your vault and git repositories for the past seven days. This generates a standardized report highlighting accomplishments and upcoming priorities.

You should not use an automated productivity summary if your local repositories lack sufficient git commit history or if your vault directory structures are not organized for file modification tracking.