changelog

To generate a changelog blog post from recent git commits, you ask the Skill to draft a changelog. It reads your latest blog post to find the cutoff date, aggregates subsequent commits, and groups them semantically into Added, Fixed, and Improved sections.

Yes, you can automatically group commit summaries into Added, Fixed, and Improved sections. The Skill semantically groups changes by area and formats them for blog publication, producing a structured and consistent narrative.

You can format git history into a ready-to-publish blog draft by having the Skill summarize recent commits. It enforces frontmatter and section structure, applying publish-ready styling to produce a consistent post in your blog directory.

Yes, this changelog automation works with your project's existing blog format. The Skill drafts changelog posts by summarizing recent commits using your project's standard blog format to ensure consistent, publication-ready output.

The best way to automate changelog documentation from commit history is to use this Skill. It reads the latest post to determine the cutoff date, aggregates subsequent commits, and generates a formatted draft grouped by Added, Fixed, and Improved categories.

To find the cutoff date for summarizing commits in a new changelog post, the Skill reads your latest blog post. It uses this date to aggregate only the subsequent commits for the new draft.