write-changelog

Generate changelog entries from archived tickets and update CHANGELOG.md.

1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/qmu/workaholic --skill write-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-changelog
Source: https://github.com/qmu/workaholic/tree/main/plugins/core/skills/write-changelog
Command: npx skills add https://github.com/qmu/workaholic --skill write-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automatically generates and updates the project's CHANGELOG.md by transforming archived tickets into structured release notes, ensuring release documentation stays current.

Core Features & Use Cases

  • Generate changelog entries from archived tickets stored under .workaholic/tickets/archive for a given branch.
  • Categorize entries by Added, Changed, and Removed, and prepend them to CHANGELOG.md to reflect the latest changes.
  • Useful for release workflows, PR descriptions, and audit trails of changes across multiple tickets.

Quick Start

Run the bundled script to generate the changelog entries: bash .claude/skills/write-changelog/sh/generate.sh <branch-name> <repo-url>

Frequently Asked Questions about write-changelog

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

FAQPage Schema
How do I automatically generate changelog entries from archived tickets?

You can generate changelog entries by running a provided shell script that reads archived tickets from .workaholic/tickets/archive and prepends structured release notes directly into CHANGELOG.md.

How do I update CHANGELOG.md for a specific Git branch?

To update CHANGELOG.md, execute the bundled shell script with the target branch name and repository URL as arguments, which inserts categorized ticket activity at the top of the file.

Does generating release notes from tickets require a specific workflow setup?

Generating release notes requires a local Git-enabled environment and repositories tracked with Workaholic's ticket workflow, specifically needing access to archived tickets under .workaholic/tickets/archive.

How are changelog entries categorized when generated from archived tickets?

Changelog entries generated from archived tickets are categorized into Added, Changed, and Removed sections, reflecting recent ticket activity before being prepended to CHANGELOG.md.

What is the best way to maintain release documentation across multiple tickets?

Automating CHANGELOG.md updates from archived tickets ensures release documentation stays current, providing a reliable audit trail of changes across multiple tickets for release workflows.

Can I use this changelog automation without Workaholic's ticket workflow?

No, this changelog automation explicitly requires repositories tracked with Workaholic's ticket workflow to access the archived tickets needed for generating structured release notes.