skills.rest
marius4lui
marius4luiCOMMUNITY
Explore all skills by this author →
Website𝕏@marius4luiGitHub

versioning

Enforce Classly versioning workflow under versions/ for plans, notes, and changelogs.

1|Updated Jan 4, 2026
Search Tags:#planning#changelog#release management#versioning#commit messages
One-click install
npx skills add https://github.com/marius4lui/Classly --skill versioning-marius4lui
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: versioning
Source: https://github.com/marius4lui/Classly/tree/main/.agents/skills/Versioning
Command: npx skills add https://github.com/marius4lui/Classly --skill versioning-marius4lui

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of managing software versions, including planning, committing, and documenting changes for the Classly project.

Core Features & Use Cases

  • Version Planning: Create detailed plans for new releases.
  • Commit Message Generation: Enforce conventional commit messages.
  • Changelog Maintenance: Keep release notes up-to-date.
  • Use Case: When a developer needs to prepare for releasing version 1.2.0, they can use this Skill to generate a plan, draft the commit messages for all changes, and update the changelog.

Quick Start

Use the versioning skill to create a plan for version 1.1.0.

Frequently Asked Questions about versioning

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

FAQPage Schema
How do I manage software versioning plans and changelogs in markdown?▼

Software versioning plans and changelogs are managed by creating detailed markdown release plans and maintaining version artifacts like Commit.md and Readme.md within version-specific directories.

What's the best way to generate conventional commit messages for a new release?▼

Conventional commit messages for a new release are generated by enforcing a structured versioning workflow that drafts commit messages for all planned changes within a dedicated version directory.

How do I create a detailed plan for version 1.2.0 release?▼

To create a detailed plan for a version 1.2.0 release, you request a new version plan using the versioning workflow, which generates a structured markdown plan outlining the release steps.

Can I maintain release notes and changelogs under a versions directory?▼

Yes, you can maintain release notes and changelogs under a versions directory, where the workflow manages version-specific artifacts including Commit.md and Readme.md files.

Does version planning work with markdown files for documenting software releases?▼

Version planning works directly with markdown files to document software releases, facilitating the creation of detailed plans and keeping changelogs up-to-date within structured directories.

Why use a structured workflow for commit messages and changelog maintenance?▼

A structured workflow for commit messages and changelog maintenance ensures consistent versioning conventions, streamlines the documentation of changes, and organizes release artifacts systematically.

Related Skills

Explore More Software Engineering Skills→
trueratruera
3.5k

trulens-dataset-curation

Create and curate ground-truth evaluation datasets for TruLens.

Official
Intermediate
chrislyonschrislyons

git.release.prep

Automates release prep with semantic versioning, changelog generation, and GitHub publishing.

Community
Intermediate
nanorepublicananorepublica
61

Global Tech Stack

Validate code against centralized global tech stack standards.

Community
Basic
aaaa47080aaaa47080
4

release

Automate git releases with changelog generation and semantic versioning.

Community
Intermediate