update-changelog

Update changelog entries and synchronize versions across JSON, TypeScript, and package metadata.

3|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/YanCheng-go/danskprep --skill update-changelog-yancheng-go
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-changelog
Source: https://github.com/YanCheng-go/danskprep/tree/main/.claude/skills/update-changelog
Command: npx skills add https://github.com/YanCheng-go/danskprep --skill update-changelog-yancheng-go

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Add a new changelog entry, bump the version, and synchronize all three version locations to keep release notes and metadata aligned across the codebase.

Core Features & Use Cases

  • Generate a new top entry in src/data/seed/changelog.json with version, date, title, highlights, and stats.
  • Sync the latest version across src/lib/constants.ts and package.json to ensure consistent release numbering.
  • Validate changes by running the build steps (TypeScript checks and npm build) to catch regressions before release.
  • Use in release pipelines to streamline QA, documentation, and artifact consistency for PD3 Module 2 seed data.

Quick Start

Run the update-changelog workflow to create a new changelog entry, bump the version, and sync all three locations.

Frequently Asked Questions about update-changelog

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

FAQPage Schema
How do I automate changelog updates and version synchronization across multiple files?

Automate changelog updates by reading the current changelog, computing highlights, bumping the version, and prepending a new top entry. This process synchronizes version numbers across seed data, code constants, and package metadata automatically.

What's the best way to keep version numbers aligned in package.json and TypeScript constants?

Keep version numbers aligned by syncing the latest version across package.json, TypeScript constants files, and seed data JSON. This ensures consistent release numbering and metadata alignment throughout the codebase during release workflows.

How do I validate a TypeScript build before publishing a new release version?

Validate a TypeScript build by running build checks with TypeScript and npm after updating the changelog and bumping the version. This catches regressions and ensures artifact consistency before release.

Can I generate a new changelog entry with highlights and stats automatically?

Generate a new changelog entry automatically in seed data JSON with version, date, title, highlights, and stats. The workflow computes highlights and prepends the entry to the existing changelog history.

Does this changelog automation work with seed data workflows?

This changelog automation works with seed data workflows by updating src/data/seed/changelog.json and synchronizing versions across src/lib/constants.ts and package.json, streamlining QA and documentation for seed data release pipelines.

Why do I need build validation when bumping versions in a release pipeline?

Build validation is needed when bumping versions to catch regressions introduced by version synchronization. Running TypeScript checks and npm build ensures the codebase compiles correctly and artifacts remain consistent before release.