swpm-keepachangelog

Enforce Keep a Changelog 1.1.0 formatting for SWPM CHANGELOG.md entries.

125|5|Updated May 13, 2022
One-click install
npx skills add https://github.com/deinsoftware/swpm --skill swpm-keepachangelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swpm-keepachangelog
Source: https://github.com/deinsoftware/swpm/tree/main/.agents/skills/swpm-keepachangelog
Command: npx skills add https://github.com/deinsoftware/swpm --skill swpm-keepachangelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keep a Changelog 1.1.0 standards for SWPM. Defines format, sections, and conventions for CHANGELOG.md entries. Activates when user modifies CHANGELOG.md.

Core Features & Use Cases

  • Ensures an Unreleased section exists and proper heading structure
  • Enforces standard sections: Added, Changed, Deprecated, Removed, Fixed, Security
  • Validates date formats and release version formatting per Keep a Changelog 1.1.0

Quick Start

Apply Keep a Changelog 1.1.0 formatting to your CHANGELOG.md entries immediately.

Frequently Asked Questions about swpm-keepachangelog

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

FAQPage Schema
How do I format a changelog to follow Keep a Changelog 1.1.0 standards?

To format a changelog to Keep a Changelog 1.1.0 standards, maintain an Unreleased header, use standard sections like Added and Fixed, and apply ISO 8601 dates for release versions.

What sections should a changelog include for proper release notes documentation?

Proper changelog documentation requires six standard sections: Added, Changed, Deprecated, Removed, Fixed, and Security. These standard categories organize release notes clearly for readers tracking updates.

How do I structure the Unreleased section in a markdown changelog?

Structure the Unreleased section in a markdown changelog by placing it at the top, followed by standard categories like Added or Fixed. It groups notes before assigning a formal release version.

What date format does Keep a Changelog require for version entries?

Keep a Changelog requires ISO 8601 date formats for version entries. Using ISO 8601 dates ensures your changelog remains chronologically sortable and compliant with formatting standards.

Can I use custom categories instead of standard sections in my changelog?

You cannot use custom categories instead of standard sections in a compliant changelog. Keep a Changelog 1.1.0 enforces specific section headers like Added, Changed, Deprecated, Removed, Fixed, and Security.