Weekly Change Tracker

Session-end change extraction. When the developer wraps up work, read the conversation context and produce structured change entries that capture the why behind changes — intent, exploration paths, and reasoning that git commits rarely convey.

Zero-Config Mode

This skill works with or without a configured knowledge vault:

• With vault: entries are written to {vault}/raw/weeks/{ISO-week}/{project-slug}.json and a brief confirmation is shown.
• Without vault: entries are rendered as structured Markdown directly in the conversation. No files written, no directories created. A one-line setup hint follows the output.

The zero-config mode is the default first experience. Value before configuration.

How It Works

Step 1: Analyze Conversation Context

Read the full conversation history for this session. Start with the decision landscape — understand what problems were being solved, what alternatives were considered, what trade-offs were accepted. The concrete changes (files, commits) are evidence for decisions, not the primary output.