changelog

Insert categorized changelog entries into readme.txt under the Unreleased section.

316|74|Updated Apr 15, 2013
One-click install
npx skills add https://github.com/bonny/WordPress-Simple-History --skill changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/bonny/WordPress-Simple-History/tree/main/.claude/skills/changelog
Command: npx skills add https://github.com/bonny/WordPress-Simple-History --skill changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides you to add a changelog entry to the Simple History plugin's readme.txt, ensuring it follows the project's changelog format and lands under the Unreleased section so users can quickly see what changed.

Core Features & Use Cases

  • Structured entries: Add a one-line changelog entry categorized as Added, Changed, Fixed, Deprecated, Removed, or Security.
  • Format accuracy: Ensures entries follow the WordPress changelog conventions for clarity and consistency.
  • Workflow alignment: Useful whenever releasing a new version or when a user asks to update the changelog.

Quick Start

  • Ask the user for the changelog entry text (one line summary of the change)
  • Determine the category - Added, Changed, Fixed, Deprecated, Removed, or Security
  • Read the readme.txt file to locate the ## Changelog section
  • Find the ### Unreleased subsection
  • Add the new entry under the appropriate category within Unreleased, following the required format
  • Show the user the added entry and confirm it looks correct

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I add a changelog entry to readme.txt?

Adding a changelog entry to readme.txt involves locating the Unreleased section under the Changelog heading, then inserting a one-line summary formatted as '- [Category] description' under the appropriate category (Added, Changed, Fixed, Deprecated, Removed, or Security) to keep your WordPress plugin's release notes current.

What format should changelog entries follow?

Changelog entries follow WordPress conventions with the format '- [Category] description', where Category is one of Added, Changed, Fixed, Deprecated, Removed, or Security. Entries go under the ### Unreleased subsection so users immediately see unreleased changes.

When should I update the Unreleased section of my changelog?

Update the Unreleased section whenever you make a change to your plugin that users need to know about—new features, bug fixes, security patches, or deprecations. Documenting changes in Unreleased keeps your changelog accurate and ready for the next release.

Can I categorize changelog entries by change type?

Yes, changelog entries are categorized into six types: Added for new features, Changed for modifications, Fixed for bug fixes, Deprecated for features being phased out, Removed for deletions, and Security for vulnerability patches. This structure helps users quickly find relevant changes.

Does this work with WordPress plugin readme.txt files?

Yes, this is specifically designed for the Simple History plugin's readme.txt file. It automates adding entries to the Unreleased section following WordPress plugin changelog conventions for clarity and consistency across releases.