skills.rest
NASA-AMMOS
NASA-AMMOSOFFICIAL
Explore all skills by this author →
WebsiteGitHub

slim-changelog

Automates CHANGELOG.md creation and maintenance with Keep a Changelog structure and semantic versioning guidance.

35|14|Updated Feb 16, 2022
Search Tags:#template#changelog#versioning#documentation#communication#release notes#Keep a Changelog
One-click install
npx skills add https://github.com/NASA-AMMOS/slim --skill slim-changelog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: slim-changelog
Source: https://github.com/NASA-AMMOS/slim/tree/main/static/marketplace/skills/slim-changelog
Command: npx skills add https://github.com/NASA-AMMOS/slim --skill slim-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill helps teams create and maintain human-readable CHANGELOG.md files that clearly communicate software changes to users and contributors, aligning with Keep a Changelog standards.

Core Features & Use Cases

  • Template-driven CHANGELOG creation following Keep a Changelog
  • Guided release-note entry structure with sections Added, Changed, Deprecated, Removed, Fixed, and Security
  • Supports onboarding and transparent communication about project evolution

Quick Start

Copy the assets/CHANGELOG.md template into your project as CHANGELOG.md, customize the header, and add your first release entry with a semantic version and date. For ongoing development, update the changelog with new sections for each release.

Frequently Asked Questions about slim-changelog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a human-readable changelog for my software project?▼

To create a human-readable changelog, copy the Keep a Changelog template into your project as CHANGELOG.md, customize the header, and add your first release entry with a semantic version and date.

What sections should I include in release notes following Keep a Changelog?▼

Keep a Changelog release notes should include the sections Added, Changed, Deprecated, Removed, Fixed, and Security to transparently communicate software evolution to users and contributors.

What's the best way to maintain changelog entries during ongoing development?▼

The best way to maintain changelog entries is using a template-driven workflow where you update CHANGELOG.md with new sections for each release as development progresses.

Does this changelog template enforce semantic versioning guidance?▼

Yes, this changelog template enforces semantic versioning guidance alongside the Keep a Changelog structure to ensure clear communication about project versioning and release changes.

Can I use this changelog template for onboarding new contributors?▼

Yes, you can use this Keep a Changelog template for onboarding because it supports transparent communication about project evolution and clearly documents software changes for new contributors.

Why do I need a standardized format for documenting project changes?▼

You need a standardized changelog format to clearly communicate software changes to users and contributors, aligning with Keep a Changelog standards for transparent and consistent release documentation.

Related Skills

Explore More Content & Communication Skills→
fockusfockus
2

harness-release

Automate Harness v3 release workflows with version bumps, changelog updates, and GitHub Releases.

Community
Advanced
opensupplyhubopensupplyhub
20

release-notes

Generate formatted release notes from git logs, PRs, and migration files.

Official
Intermediate
bmad-code-orgbmad-code-org
8

bmad-os-changelog

Generate structured changelog entries from git history and pull request metadata.

Official
Intermediate
ThomashighbaughThomashighbaugh
1

changelog-generator

Generate structured Markdown release notes from categorized git commit histories.

Community
Intermediate