What problem does it solve? Keeping per-component CHANGELOG.md files accurate is tedious: each Lucca Front component documents only user-visible changes, and its history spans multiple package paths (prisme, ng, scss, and annex packages) due to an ongoing migration. This Skill automates identifying published versions, collecting relevant commits, and writing correctly formatted changelog entries. ## Core Features & Use Cases - Version range detection: Reads the last documented version from the CHANGELOG header and cross-references git tags and GitHub releases to find what needs documenting. - Multi-path commit collection: Runs git log across packages/prisme, packages/ng (pre-migration history), packages/scss, and annex packages like packages/icons so no relevant commit is missed. - Precise version attribution: Uses git tag --contains to find the first stable release containing each commit, avoiding misattribution from range boundaries. - Standardized formatting: Classifies changes into Added/Changed/Deprecated/Removed/Fixed sections and writes English entries in the required markdown format. - Use Case: After a Lucca Front release, ask the Skill to update the button component's changelog; it will gather commits since the last documented version, assign each to the correct release, and append properly formatted entries. ## Quick Start Update the CHANGELOG.md for the button component with all changes published since its last documented version.
