versioning

Manage Markdown document versioning by updating frontmatter metadata.

Updated Feb 25, 2026

Search Tags:#changelog #versioning #documentation #markdown #semantic versioning #frontmatter

Ready to run

npx skills add https://github.com/perfectuser21/cecelia --skill versioning-perfectuser21

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: versioning
Source: https://github.com/perfectuser21/cecelia/tree/main/packages/workflows/skills/versioning
Command: npx skills add https://github.com/perfectuser21/cecelia --skill versioning-perfectuser21

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps manage the evolution of documents by automatically adding and updating version information in their frontmatter, ensuring clear tracking of changes over time.

Core Features & Use Cases

Automated Versioning: Adds and updates id, version, created, updated, and changelog fields in Markdown frontmatter.
Semantic Versioning: Follows standard rules for patch, minor, and major version increments.
ID Generation: Creates consistent, path-based IDs for files.
Use Case: When you update a project's documentation, this Skill ensures each version is clearly marked, making it easy to see what changed between releases and to revert to older versions if necessary.

Quick Start

Use the versioning skill to add frontmatter versioning to the file 'README.md'.

Frequently Asked Questions about versioning

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

FAQPage Schema

How do I track document evolution in Markdown files?▼

Markdown document evolution is tracked by automatically adding and updating frontmatter metadata fields such as id, version, created, updated, and changelog, ensuring clear historical tracking of changes over time.

How does semantic versioning work for documentation?▼

Semantic versioning for documentation follows standard rules for patch, minor, and major version increments, updating the version field in the frontmatter to reflect the scale of document changes.

What is the best way to add a changelog to Markdown frontmatter?▼

Adding a changelog to Markdown frontmatter is best handled automatically by inserting and updating a changelog field during document updates, capturing what changed between releases directly in the metadata.

Can I generate path-based IDs for Markdown files automatically?▼

Path-based IDs for Markdown files can be generated automatically, creating consistent IDs derived from file paths to facilitate document lifecycle management and historical tracking.

When do I need frontmatter metadata for document lifecycle management?▼

Frontmatter metadata for document lifecycle management is needed when updating project documentation to clearly mark each version, making it easy to see changes and revert to older versions if necessary.