Changelog
Skill NSBen/skillfoundry/src/skillfoundry/data/starter_skills/changelog
🔥 SkillFoundry (forge) — open, vendor-neutral toolchain for authoring, validating, testing & publishing AI agent skills. Works across Claude Code / Cursor / Codex / OpenCode / Cline. Ships 15 starter skills.
npx -y skills add NSBen/skillfoundry --skill changelogAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 13 days oldThe repository was created 13 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when you cut a release or want a CHANGELOG entry derived from conventional commits and PRs without hand-writing it.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.0 KB, as published. Nobody here has run it
Changelog
When to use
Use this skill before a release, or when the CHANGELOG is stale and needs a new section.
Steps
- Collect commits since the last tag (
git log <last>..HEAD). - Group them by type: Added, Changed, Fixed, Deprecated, Removed, Security.
- Turn each into a one-line user-facing note; drop internal/chore noise.
- Link to PRs or issues where available.
- 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").