wtf.changelog

Generate changelog entries and GitHub Release notes from Epic, Feature, and Task hierarchies.

7|2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/xiduzo/wtf --skill wtf-changelog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wtf.changelog
Source: https://github.com/xiduzo/wtf/tree/main/skills/wtf.changelog
Command: npx skills add https://github.com/xiduzo/wtf --skill wtf-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of changelog entries and release notes by deriving user-facing language from the project spec hierarchy (Epics, Features, Tasks) rather than raw commit messages.

Core Features & Use Cases

  • Generate changelog entries and GitHub Release notes from Epic → Feature → Task hierarchies.
  • Derive user-facing language from Gherkin scenarios and Acceptance Criteria, not raw commit messages.
  • Update CHANGELOG.md and/or create GitHub Releases with concise, outcome-focused descriptions.

Quick Start

Draft a changelog entry for the latest merged Epic or Feature.

Frequently Asked Questions about wtf.changelog

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

FAQPage Schema
How do I generate release notes from merged GitHub work instead of raw commit messages?▼

You can generate release notes by deriving user-facing language from your spec hierarchy, such as Epics, Features, and Tasks. This approach uses Gherkin scenarios and Acceptance Criteria to produce concise, outcome-focused narratives for your changelog.

Does this skill format changelog entries following Keep a Changelog conventions?▼

Keep a Changelog conventions are applied when creating your changelog entries. This ensures traceability and consistency across versions while updating your CHANGELOG.md file with structured, outcome-focused release information.

Can I create GitHub Releases from Epic and Feature hierarchies automatically?▼

You can create GitHub Releases from Epic and Feature hierarchies automatically. The skill derives user-facing language from your project specifications to populate the release with concise descriptions.

What is the best way to automate changelog entries for Gherkin acceptance criteria?▼

Automating changelog entries for Gherkin acceptance criteria involves deriving user-facing language directly from the spec hierarchy. This method transforms scenarios into structured CHANGELOG.md updates following Keep a Changelog conventions.

How do I draft a changelog entry for a recently merged Epic?▼

Drafting a changelog entry for a merged Epic involves deriving user-facing language from the Epic's associated Features and Tasks. The skill generates concise, outcome-focused narratives suitable for CHANGELOG.md or GitHub Releases.