skills.rest
Zelenov
ZelenovCOMMUNITY
Explore all skills by this author →
Website𝕏@zelenovGitHub

create-release-version

Create and update release notes in version.md with H1 headers and Added or Changed sections.

1|Updated Jan 23, 2026
Search Tags:#automation#versioning#documentation#markdown#project-management#release-notes
One-click install
npx skills add https://github.com/Zelenov/frename --skill create-release-version
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-release-version
Source: https://github.com/Zelenov/frename/tree/main/.claude/skills/create-release-version
Command: npx skills add https://github.com/Zelenov/frename --skill create-release-version

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool helps maintain release notes by automatically creating or updating version entries in version.md, ensuring consistency with the required structure.

Core Features & Use Cases

  • Create new version blocks at the top of version.md following the specified format.
  • Update existing version entries when releasing or revising notes.
  • Ensure that each version block includes a valid header and at least one of the Added or Changed sections.

Quick Start

Add a new H1 block at the top of version.md with the new version number and fill in its Added and/or Changed sections accordingly.

Frequently Asked Questions about create-release-version

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

FAQPage Schema
How do I automate release notes creation in a markdown file?▼

To automate release notes creation, this Skill adds or updates version entries directly in your version.md file, ensuring a valid H1 version header and at least one Added or Changed section are present.

What format should release notes follow when cutting a new software version?▼

Release notes require an H1 version header at the top of version.md, followed by at least one Added or Changed section to document new features or modifications for that release.

How do I update existing release history in version.md without breaking the structure?▼

You can update existing release entries by modifying the specific version block, while the Skill validates that the H1 header and the Added or Changed sections remain intact and correctly formatted.

Can I use this for project management documentation if I only have a Removed section?▼

No, this Skill requires at least one Added or Changed section to be present in the version block. A Removed section alone will not meet the structural validation requirements for the release notes.

Does this release versioning automation work without external dependencies?▼

Yes, this release versioning automation operates independently without external dependencies, directly managing the markdown structure of your version.md file for software projects.

Related Skills

Explore More Software Engineering Skills→
stephendolanstephendolan
2

writing-documentation

Review Markdown documentation for structure, formatting, and consistency.

Community
Basic
fagemxfagemx
58

game-docs

Generate player-facing patch notes and internal changelogs from git tags and commits.

Community
Advanced
psd401psd401
2

changelog

Generate structured changelog entries from git commit history.

Official
Intermediate
DrLuggelsDrLuggels
3

changelog-automation

Generate changelogs and release notes from Conventional Commits.

Community
Advanced