What problem does it solve? Keeping a public project journal current is tedious: someone must read weeks of commits, decide what actually matters, and write readable summaries. This Skill automates that biweekly loop while keeping a human in the approval seat. ## Core Features & Use Cases - Commit-to-theme curation: Reads git history since the last curated bookmark and consolidates commits into one or two plain-English thematic entries, never raw commit digests. - Editorial standards enforcement: Applies strict rules for titles, body length, arc continuation, and omission of themeless chores so the timeline stays skimmable. - Safe branch-based workflow: Builds changes in a temporary git worktree on a dated branch, runs the validator and website build, and hands off a report for approval without pushing, merging, or deploying. - Use Case: A maintainer runs the biweekly loop to turn two weeks of design-system commits into a single journal entry like "The design system publishes to npm", reviewed and merged by a human. ## Quick Start Ask the assistant to update the project journal by running the site updates loop.
