addon-changelog

Generate changelog entries for add-on packages from git tags and pull requests.

Updated May 11, 2026
One-click install
npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill addon-changelog-thachrocky12345
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: addon-changelog
Source: https://github.com/thachrocky12345/local-agent-train-workstation/tree/main/qvac/.cursor/skills/addon-changelog
Command: npx skills add https://github.com/thachrocky12345/local-agent-train-workstation --skill addon-changelog-thachrocky12345

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing release notes for add-on packages is tedious and error-prone: you must verify version bumps, diff against the previous release tag, collect merged PRs, and format everything so the automated GitHub release workflow can parse it. This Skill automates that entire changelog generation workflow. ## Core Features & Use Cases - Mandatory version bump validation: Compares the add-on's package.json version between main and HEAD, and stops with a warning if no bump is detected. - Package-scoped release diffing: Resolves the previous release tag (e.g., llamacpp-embed-v0.10.7) and computes diffs and commit logs limited to the target package path. - PR collection and filtering: Extracts PR numbers from commit messages, fetches titles and URLs via gh pr view, and drops PRs that don't touch the target package. - Workflow-compatible formatting: Writes a structured CHANGELOG.md version block (## [X.Y.Z] - YYYY-MM-DD) with narrative sections and a Pull Requests list that the GitHub release workflow can extract. - Use Case: Before merging a release PR for an add-on, invoke the skill to produce a complete, human-readable changelog entry covering all changes since the last released tag. ## Quick Start Generate the changelog entry for the llamacpp-embed add-on package for the upcoming release.

Frequently Asked Questions about addon-changelog

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

FAQPage Schema
How do I generate a changelog for an add-on package release?

Invoke the skill and specify the target add-on package. It validates the version bump in package.json, diffs the previous release tag against HEAD scoped to the package path, collects related PRs, and writes a formatted CHANGELOG.md version block.

What happens if the package.json version is not bumped?

The skill stops and displays a warning that the version in packages/<addon>/package.json is unchanged compared to main. You must bump the version, commit and push it, then re-run the command before a changelog is generated.

How does the changelog workflow find the previous release tag?

It reads the tag_name format from .github/workflows/create-github-release.yml and builds the upstream tag for the previous version, using the pattern <short_addon_name>-v<version>. If the tag is missing, it falls back to diffing main...HEAD with a warning.

Why must the changelog use the ## [X.Y.Z] - YYYY-MM-DD format?

The GitHub release workflow extracts the release body from CHANGELOG.md by taking text after the version heading until the next ## [ heading. Content outside that block is not included in the automated GitHub release.

Does the changelog include PRs that touch other packages?

No. PR numbers are extracted from commits scoped to the target package path, and each PR is verified with gh pr view --json files. PRs that do not touch files under packages/<addon>/ are dropped from the release notes.