Skip to content
cccskills
FreePublished on GitHub

semantic-versioning

Manages project versioning following Semantic Versioning (SemVer) principles. Calculates increments based on changes and synchronizes version across documentation and metadata. Use when the user asks to "bump the version", "prepare a release", or when the `changelog` skill calls for a release.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Semantic Versioning Skill

Instructions

1. Detect Current Version

  • Read the latest version from CHANGELOG.md (e.g., the most recent header ## [X.Y.Z]).
  • Read the version from .github/repository-metadata.json.
  • If they differ, flag the mismatch to the user and ask which is authoritative.

2. Analyze Changes

Scan the changes since the last release:

  • If using changelog skill: Look at the items under [Unreleased] or the new version block being prepared.
  • If using git log: Scan for Conventional Commits types.

3. Determine Increment Type

Follow these priority rules:

  1. MAJOR (X.0.0): Any "BREAKING CHANGE" footer or ! after the type (e.g., feat!:).
  2. MINOR (x.Y.0): Any feat commit or "Added" entry in the changelog.
  3. PATCH (x.y.Z): Any fix, perf, refactor commit or "Fixed"/"Changed" entry in the changelog.
  4. No Change: If only docs, chore, style, test, build, or ci changes are found, default to PATCH unless the user specifies otherwise.

4. Apply Version Update

Update the following files in a single pass:

  • CHANGELOG.md: Rename the ## [Unreleased] section to ## [NEW_VERSION] - CURRENT_DATE or update the latest entry.
  • .github/repository-metadata.json: Update the "version" field.

Quality Gates

  • Version follows MAJOR.MINOR.PATCH format.
  • No regression in version number.
  • All version-tracking files are synchronized.
  • Date in CHANGELOG.md is in YYYY-MM-DD format.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Generates and maintains changelogs following Keep a Changelog format. Use when updating release notes, finishing tasks, or tagging versions. For version bumps, see semantic-versioning.

The English summary is being prepared. Showing the original description.

tuliosousapro/SaaS-blueprint5Updated Aug 31, 2026

Structured competitor teardown skill. Use when scraping competitor sites, extracting pricing/features/positioning, or analyzing strategic gaps. For general research, see market-research.

The English summary is being prepared. Showing the original description.

tuliosousapro/SaaS-blueprint5Updated Aug 31, 2026

Enforces Conventional Commits format for git commit messages. Use when formatting commits or validating message structures. For git commands, see git-control.

The English summary is being prepared. Showing the original description.

tuliosousapro/SaaS-blueprint5Updated Aug 31, 2026

Creates an llms.txt file from scratch based on repository structure. Use when configuring LLM discovery files. For updating existing configurations, see update-llms.

The English summary is being prepared. Showing the original description.

tuliosousapro/SaaS-blueprint5Updated Aug 31, 2026

Intelligent README.md generation prompt that analyzes project documentation structure and creates comprehensive repository documentation. Scans ./ directory files and creates a README.md file for the project. Only used when creating a new repository. or when the README.md file is missing.

The English summary is being prepared. Showing the original description.

tuliosousapro/SaaS-blueprint5Updated Aug 31, 2026

Standardizes git operations, branch management, and disaster recovery. Use when committing, branching, or resolving conflicts. For commit formatting, see conventional-commits.

The English summary is being prepared. Showing the original description.

tuliosousapro/SaaS-blueprint5Updated Aug 31, 2026

See all skills by tuliosousapro

Report a problem with this skill