changelog-root — automated changelog updates changelog-root, community, automated changelog updates, ide skills, change type identification, Claude Code, Cursor, Windsurf

v1.0.0
GitHub

About this Skill

Ideal for Version Control Agents requiring automated ChangeLog management and consistent versioning. changelog-root is a skill that automates the update of the root ChangeLog entry, ensuring consistent versioning and accurate release information.

Features

Identifies change types (patch, minor, major) for accurate versioning
Reads the top entry in ChangeLog to determine if it's UNRELEASED
Finds the latest released version from the first dated entry
Computes the target version based on the latest released version and change type
Updates the root ChangeLog entry to maintain consistency

# Core Topics

automated changelog updates change type identification
ts-klassen ts-klassen
[0]
[0]
Updated: 3/6/2026

Agent Capability Analysis

The changelog-root skill by ts-klassen is an open-source community AI agent skill for Claude Code and other IDE workflows, helping agents execute tasks with better context, repeatability, and domain-specific guidance. Optimized for automated changelog updates, change type identification.

Ideal Agent Persona

Ideal for Version Control Agents requiring automated ChangeLog management and consistent versioning.

Core Value

Empowers agents to maintain accurate version lists and update root ChangeLog entries by identifying change types such as patch, minor, or major, ensuring consistent versioning and automating the process of reading and updating ChangeLog files.

↓ Capabilities Granted for changelog-root

Automating ChangeLog updates for new releases
Identifying and categorizing changes as patch, minor, or major
Maintaining consistent versioning across the project

! Prerequisites & Limits

  • Requires access to the ChangeLog file
  • Limited to projects using a ChangeLog file for version tracking
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

changelog-root

Install changelog-root, an AI agent skill for AI agent workflows and automation. Works with Claude Code, Cursor, and Windsurf with one-command setup.

SKILL.md
Readonly

Changelog Root

Overview

Update the root ChangeLog entry and keep the root release version and version lists consistent.

Versioning

  1. Identify the change type (patch, minor, major). Ask if unclear.
  2. Read the top entry in ChangeLog and note whether it is UNRELEASED.
  3. Find the latest released version from the first dated entry.
  4. Compute the target version from the latest released version and the change type:
    • Patch: fixes, docs, or internal changes without new features.
    • Minor: new features or notable behavior changes.
    • Major: breaking changes.
  5. Apply one of these states:
    • No UNRELEASED entry: insert a new UNRELEASED entry at the top with the target version.
    • UNRELEASED exists but target version is higher: update the * VERSION: line to the target version.
    • UNRELEASED exists and target version is the same or lower: keep the * VERSION: line unchanged.
  6. Never downgrade an existing UNRELEASED version.
  7. Update rebar.config at {release, {qrpc, "X.Y.Z"}, ...} to match the UNRELEASED version.
  8. Do not replace UNRELEASED with a date; only do that at release time.

Scope and Forbidden Reads

Only edit the repository root ChangeLog. Do not open or modify any other ChangeLog files in the repo. It is forbidden to read apps/*/ChangeLog or config/pkgsrc/files/*/*/ChangeLog for this task unless you edited them or asked to do so.

Subsystem Versioning

Refresh * SUBSYSTEM VERSIONS: from apps/*/src/*.app.src (vsn values) if you edited them or asked to do so. Keep the existing order and formatting. Do not read new ChangeLog files just for this. If you are not sure what to do, skip this section.

Package Versioning

Refresh * PACKAGE VERSIONS: from config/pkgsrc/files/meta-pkgs/*/Makefile (DISTNAME versions) if you edited those meta-pkg files or were asked to do so. Keep the existing order and formatting. Do not add versions for non-meta packages; their ChangeLogs (example: config/pkgsrc/files/audio/voicevox_core/ChangeLog) do not affect the root ChangeLog. Do not read new ChangeLog files just for this. If you are not sure what to do, skip this section.

Change Description

Append the new change line(s) under the version lists in the UNRELEASED entry.

Formatting Rules

Use the existing ChangeLog formatting:

  • Use a header line like UNRELEASED ts-klassen <qrpc@su-shiki.com> or YYYY-MM-DD ts-klassen <qrpc@su-shiki.com>.
  • Keep a blank line after the header.
  • Use tabs for indentation and * bullets, matching the file.
  • Use 2 new lines in between entries.

Example Requests

  • "Update ChangeLog"
  • "Update ChangeLog as minor update"
  • "Update the root ChangeLog and rebar.config release version to 0.2.0."

Example scenario

No UNRELEASED

current file:

2025-12-25  ts-klassen  <qrpc@su-shiki.com>

	* VERSION: 0.1.0
	* SUBSYSTEM VERSIONS:
		* qrpc: 0.1.0
		* q_tut: 0.3.0
		* q_vvx: 0.1.0
	* PACKAGE VERSIONS:
		* qrpc-devel: 0.1.0
		* qrpc-prod: 0.1.0
	Initial setup.

updated file:

UNRELEASED  ts-klassen  <qrpc@su-shiki.com>

	* VERSION: 0.2.0
	* SUBSYSTEM VERSIONS:
		* qrpc: 0.1.0
		* q_tut: 0.3.0
		* q_vvx: 0.1.0
	* PACKAGE VERSIONS:
		* qrpc-devel: 0.1.0
		* qrpc-prod: 0.1.0
	Added some feature.


2025-12-25  ts-klassen  <qrpc@su-shiki.com>

	* VERSION: 0.1.0
	* SUBSYSTEM VERSIONS:
		* qrpc: 0.1.0
		* q_tut: 0.3.0
		* q_vvx: 0.1.0
	* PACKAGE VERSIONS:
		* qrpc-devel: 0.1.0
		* qrpc-prod: 0.1.0
	Initial setup.

UNRELEASED 0.1.1 to 0.2.0

current file:

UNRELEASED  ts-klassen  <qrpc@su-shiki.com>

	* VERSION: 0.1.1
	* SUBSYSTEM VERSIONS:
		* qrpc: 0.1.0
		* q_tut: 0.3.0
		* q_vvx: 0.1.0
	* PACKAGE VERSIONS:
		* qrpc-devel: 0.1.0
		* qrpc-prod: 0.1.0
	Fixed some bug.


2025-12-25  ts-klassen  <qrpc@su-shiki.com>

	* VERSION: 0.1.0
	* SUBSYSTEM VERSIONS:
		* qrpc: 0.1.0
		* q_tut: 0.3.0
		* q_vvx: 0.1.0
	* PACKAGE VERSIONS:
		* qrpc-devel: 0.1.0
		* qrpc-prod: 0.1.0
	Initial setup.

updated file:

UNRELEASED  ts-klassen  <qrpc@su-shiki.com>

	* VERSION: 0.2.0
	* SUBSYSTEM VERSIONS:
		* qrpc: 0.1.0
		* q_tut: 0.3.0
		* q_vvx: 0.1.0
	* PACKAGE VERSIONS:
		* qrpc-devel: 0.1.0
		* qrpc-prod: 0.1.0
	Fixed some bug.
	Added some feature.


2025-12-25  ts-klassen  <qrpc@su-shiki.com>

	* VERSION: 0.1.0
	* SUBSYSTEM VERSIONS:
		* qrpc: 0.1.0
		* q_tut: 0.3.0
		* q_vvx: 0.1.0
	* PACKAGE VERSIONS:
		* qrpc-devel: 0.1.0
		* qrpc-prod: 0.1.0
	Initial setup.

append to UNRELEASED

current file:

UNRELEASED  ts-klassen  <qrpc@su-shiki.com>

	* VERSION: 0.2.0
	* SUBSYSTEM VERSIONS:
		* qrpc: 0.1.0
		* q_tut: 0.3.0
		* q_vvx: 0.1.0
	* PACKAGE VERSIONS:
		* qrpc-devel: 0.1.0
		* qrpc-prod: 0.1.0
	Added some feature.


2025-12-25  ts-klassen  <qrpc@su-shiki.com>

	* VERSION: 0.1.0
	* SUBSYSTEM VERSIONS:
		* qrpc: 0.1.0
		* q_tut: 0.3.0
		* q_vvx: 0.1.0
	* PACKAGE VERSIONS:
		* qrpc-devel: 0.1.0
		* qrpc-prod: 0.1.0
	Initial setup.

updated file:

UNRELEASED  ts-klassen  <qrpc@su-shiki.com>

	* VERSION: 0.2.0
	* SUBSYSTEM VERSIONS:
		* qrpc: 0.1.0
		* q_tut: 0.3.0
		* q_vvx: 0.1.0
	* PACKAGE VERSIONS:
		* qrpc-devel: 0.1.0
		* qrpc-prod: 0.1.0
	Added some feature.
	Added more feature.


2025-12-25  ts-klassen  <qrpc@su-shiki.com>

	* VERSION: 0.1.0
	* SUBSYSTEM VERSIONS:
		* qrpc: 0.1.0
		* q_tut: 0.3.0
		* q_vvx: 0.1.0
	* PACKAGE VERSIONS:
		* qrpc-devel: 0.1.0
		* qrpc-prod: 0.1.0
	Initial setup.
  • changelog-pkg
    • If you edited a file under ./config/pkgsrc, read this too if you haven't.
  • changelog-app
    • If you edited a file under ./apps, read this too if you haven't.

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is changelog-root?

Ideal for Version Control Agents requiring automated ChangeLog management and consistent versioning. changelog-root is a skill that automates the update of the root ChangeLog entry, ensuring consistent versioning and accurate release information.

How do I install changelog-root?

Run the command: npx killer-skills add ts-klassen/qrpc/changelog-root. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for changelog-root?

Key use cases include: Automating ChangeLog updates for new releases, Identifying and categorizing changes as patch, minor, or major, Maintaining consistent versioning across the project.

Which IDEs are compatible with changelog-root?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for changelog-root?

Requires access to the ChangeLog file. Limited to projects using a ChangeLog file for version tracking.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add ts-klassen/qrpc/changelog-root. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use changelog-root immediately in the current project.

Related Skills

Looking for an alternative to changelog-root or another community skill for your workflow? Explore these related open-source skills.

View All

widget-generator

Logo of f
f

f.k.a. Awesome ChatGPT Prompts. Share, discover, and collect prompts from the community. Free and open source — self-host for your organization with complete privacy.

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

flags is a Next.js feature management skill that enables developers to efficiently add or modify framework feature flags, streamlining React application development.

★ 138.4k
⑂ 0
Browser

zustand

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

★ 72.8k
⑂ 0
AI

data-fetching

Logo of lobehub
lobehub

The ultimate space for work and life — to find, build, and collaborate with agent teammates that grow with you. We are taking agent harness to the next level — enabling multi-agent collaboration, effortless agent team design, and introducing agents as the unit of work interaction.

★ 72.8k
⑂ 0
AI