Add semantic versioning to skills and changelog #3

Closed
opened 2026-04-24 02:55:39 +00:00 by frank · 1 comment
Owner

Summary

Add semver to each skill's SKILL.md frontmatter or children.json, and convert the CHANGELOG from session-based to version-based format.

Why

Claude Code's plugin system supports versioned updates with 7-day orphan cleanup. Without version metadata, users can't tell if an update is safe or what changed.

Implementation

  • Add version field to each skill's SKILL.md frontmatter
  • Add version tracking to children.json entries
  • Convert CHANGELOG from session-based to semver-based
  • Consider GitHub Actions for automated release tagging

Effort

Small (< 1 day)

## Summary Add semver to each skill's SKILL.md frontmatter or children.json, and convert the CHANGELOG from session-based to version-based format. ## Why Claude Code's plugin system supports versioned updates with 7-day orphan cleanup. Without version metadata, users can't tell if an update is safe or what changed. ## Implementation - Add version field to each skill's SKILL.md frontmatter - Add version tracking to children.json entries - Convert CHANGELOG from session-based to semver-based - Consider GitHub Actions for automated release tagging ## Effort Small (< 1 day)
frank closed this issue 2026-04-24 13:41:49 +00:00
Author
Owner

Implemented in 48262cd.

  • version: 1.0.0 added to all 13 SKILL.md frontmatter fields
  • version field added to every entry in children.json
  • CHANGELOG converted from session-based to Keep a Changelog semver format
  • Orchestrator bumped to v1.1.0 (marketplace + versioning release)
Implemented in 48262cd. - `version: 1.0.0` added to all 13 SKILL.md frontmatter fields - `version` field added to every entry in children.json - CHANGELOG converted from session-based to [Keep a Changelog](https://keepachangelog.com/) semver format - Orchestrator bumped to v1.1.0 (marketplace + versioning release)
Sign in to join this conversation.
No description provided.