updates

Generate user-facing release notes from git history by filtering recent commits for user-visible changes and formatting them into a prioritized list of 'Feature: description' entries. This provides a concise changelog digest.

You can summarize git commits into a changelog automatically by analyzing the last 7 days of commit history, filtering for new features, device support, and fixes, then outputting a prioritized user-facing list.

The best way to create a changelog for recent feature updates is to aggregate the last 7 days of git history, filter for user-visible changes, and format entries as 'Feature: description' for a prioritized digest.

Yes, you need access to git history for the last 7 days to generate a changelog summary, as the Skill filters recent commits to detect and emphasize new features, device support, and user-facing fixes.

A changelog generator filters internal commits by analyzing 7 days of git history and selecting only user-visible changes, such as new features, device support, and fixes, then formatting them as 'Feature: description' entries.

Automated changelogs show the last 7 days of changes because the Skill is designed to generate concise, user-facing update summaries covering a weekly window, ensuring messaging highlights recent features and fixes.