changelog

Solid

Use when you cut a release or want a CHANGELOG entry derived from conventional commits and PRs without hand-writing it.

AI & Automation 1 stars 0 forks Updated 4 days ago MIT

Install

View on GitHub

Quality Score: 78/100

Stars 20%
10
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
33
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Changelog ## When to use Use this skill before a release, or when the CHANGELOG is stale and needs a new section. ## Steps 1. Collect commits since the last tag (`git log <last>..HEAD`). 2. Group them by type: Added, Changed, Fixed, Deprecated, Removed, Security. 3. Turn each into a one-line user-facing note; drop internal/chore noise. 4. Link to PRs or issues where available. 5. Prepend a new `## [version]` heading with the date. ## Examples - "Generate the CHANGELOG for v1.4.0" - "Summarize what changed since the last tag" ## References Follow Keep a Changelog format; write for the reader ("you can now…") not the commit log ("updated X").

Details

Author
NSBen
Repository
NSBen/skillfoundry
Created
4 days ago
Last Updated
4 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category