cst-changelog

Generate CHANGELOG entries and update manifest.json version numbers.

1|Updated Jul 15, 2025
One-click install
npx skills add https://github.com/KorCaptain/Valheim_Captain_SkillTree --skill cst-changelog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cst-changelog
Source: https://github.com/KorCaptain/Valheim_Captain_SkillTree/tree/main/.claude/skills/cst-changelog
Command: npx skills add https://github.com/KorCaptain/Valheim_Captain_SkillTree --skill cst-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically records CHANGELOG entries and updates manifest.json version after code changes, reducing manual release overhead and ensuring consistent documentation.

Core Features & Use Cases

  • CHANGELOG auto-generation: parses recent commits and keywords to create a concise release note.
  • Manifest version bump: automatically increments version_number in Thunderstore manifest to reflect changes.
  • Release automation hook: integrates with CI/CD to trigger during deployment and distribution.

Quick Start

Run the cst-changelog skill after completing a code change to generate a changelog entry and increment the version.

Frequently Asked Questions about cst-changelog

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

FAQPage Schema
How do I automate changelog generation and manifest version bumps for a Valheim mod?▼

To automate changelog generation and manifest version bumps, run the cst-changelog skill after code changes to parse recent commits, append entries to CHANGELOG.md, and increment the manifest.json version_number for Thunderstore deployment.

How does automatic changelog generation work from commit history?▼

Automatic changelog generation works by parsing recent commits and keywords during your development workflow to create a concise release note, which is then appended in the correct format to CHANGELOG.md.

Do I need a specific manifest format to automate Thunderstore release versioning?▼

Yes, automating Thunderstore release versioning requires a manifest.json file containing a version_number field, which the skill increments following MAJOR.MINOR.XX rules to reflect your code changes.

What's the best way to keep a Unity mod's changelog updated during CI/CD deployment?▼

The best way to keep a Unity mod's changelog updated during CI/CD deployment is using a release automation hook that triggers changelog recording and manifest versioning automatically when code changes are completed.

Can I use an automated versioning tool without manually editing CHANGELOG.md for every release?▼

Yes, you can use an automated versioning tool to skip manual edits, as it consolidates commit notes and appends a new changelog entry automatically while simultaneously bumping the manifest version_number.

Why does my manifest version_number need to follow MAJOR.MINOR.XX rules for release management?▼

Your manifest version_number needs to follow MAJOR.MINOR.XX rules for release management because Thunderstore deployment requires consistent version incrementing to properly track and distribute mod updates.