changelog

Yes, you can scope changelog generation to a single plugin by filtering results to one specific plugin directory. The skill parses git logs and maps changed file paths under plugins/<name>/ to isolate commits relevant to that individual plugin, producing targeted release notes without affecting other plugins.

Conventional commit prefixes label changelog entries by reading each commit message and categorizing features or fixes accordingly. The skill reads each plugin's plugin.json for version numbers, uses these prefixes to organize entries, and collapses related commits when appropriate to create clean, version-aware sections.

Yes, you can filter git commits by tag or date when generating release notes to scope the changelog to a specific release window. This allows you to summarize only the commits since the last release tag or a specific date, prepending the filtered entries to CHANGELOG.md.

Prepending new changelog entries to CHANGELOG.md preserves existing content by inserting new grouped sections at the top of the file. This safe updating mechanism ensures historical release notes remain intact while new plugin-scoped versions and features are added above the previous content.

Automating release notes for a multi-plugin repository is best handled by mapping git commit history to plugin directories and grouping entries by version extracted from plugin.json. This approach avoids manual error by automatically scoping changes per plugin and prepending structured entries to your changelog file.