Skip to content
changelog-pkg logo

Changelog Pkg

changelog-pkg

Update pkgsrc ChangeLog entries under config/pkgsrc/files/*/*/ChangeLog and keep Makefile version metadata in sync. Use when updating qrpc-devel or qrpc-prod ChangeLogs, updating their versions, or recording dependency changes.

SKILL.md

Full skill instructions

Changelog Pkg

Overview

Update pkgsrc ChangeLog entries and keep Makefile versions consistent. Only meta-pkgs are reflected in the repository root ChangeLog.

Workflow

  1. Identify the target package (example: qrpc-devel or qrpc-prod) under config/​pkgsrc/​files/<category>/<pkg>/ and open config/​pkgsrc/​files/<category>/<pkg>/​ChangeLog.
  2. Read the top entry in ChangeLog and check whether it is UNRELEASED.
  3. Determine the desired next version from the latest released version (first dated entry) and the change type.
  4. If an UNRELEASED entry exists:
    • If its version is lower than the desired next version, update the * VERSION: line (never lower it).
    • Update DISTNAME in the package Makefile to match the resulting UNRELEASED version.
    • If the ChangeLog includes a * PACKAGE VERSIONS: list (meta-pkgs), update it to match the DEPENDS versions in the Makefile and keep the same order.
    • Append the new change line(s) under the version list.
  5. If no UNRELEASED entry exists:
    • Insert a new UNRELEASED entry at the top with the version line and package list (meta-pkgs only).
    • Update DISTNAME in the Makefile to match the new UNRELEASED version.
    • Add the change line(s) under the list.
  6. Do not replace UNRELEASED with a date; only do that at release time.

Versioning Rules

Use semantic versioning:

  • Patch: fixes or small maintenance changes.
  • Minor: new features or notable behavior changes.
  • Major: breaking changes.

Never downgrade an existing UNRELEASED version; only raise it when needed.

If an existing UNRELEASED version is too low for the change (example: 0.1.1 but a feature is added and last release is 0.1.0), update it and sync DISTNAME.

Formatting Rules

Use the existing ChangeLog formatting:

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

Root ChangeLog Impact

Only ChangeLogs under config/​pkgsrc/​files/​meta-pkgs/​*/​ChangeLog are reflected in the repository root ChangeLog. Other packages (example: config/​pkgsrc/​files/​audio/​voicevox_core/​ChangeLog) do not trigger a root ChangeLog update.

Example Requests

You will be asked to update the Makefile mainly.

  • "Add this package to devel package."
  • "Add this package to prod package."
  • "Update version of rust-bin package to x.x.x."

Related skills

  • changelog-root
    • After updating meta-pkgs ChangeLog, update repository root ChangeLog

More Other skills

Delegate independent tasks to specialized agents working concurrently with isolated context.

295.4K 206.3K
View

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

179.7K 100.1K
View

Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.

179.7K 89.5K
View

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

179.7K 76.1K
View

Fundamental design principles for writing maintainable, testable Python code.

40.2K 21.9K
View

Modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first strategies.

40.2K 20K
View

Generate Playwright tests from scenarios using interactive browser exploration and validation.

39.7K 18.2K
View

Modern React state management with Redux Toolkit, Zustand, Jotai, and React Query for every state category.

40.2K 14.7K
View

GDPR-compliant data handling with consent management, data subject rights, and privacy controls.

40.2K 14.3K
View

Python error handling patterns including input validation, exception hierarchies, and partial failure handling. Use when implementing validation logic, designing exception strategies, handling batch processing failures, or building robust APIs.

40.2K 13.5K
View

Detailed multi-file refactor planning with safety checks and rollback guidance.

39.7K 13K
View