skills.rest
Paxeer-Network
Paxeer-NetworkOFFICIAL
Explore all skills by this author →
Website𝕏@paxeer_appGitHub

specification

Define commit message structure, types, scopes, and breaking changes.

3|2|Updated Feb 11, 2026
Search Tags:#git#changelog#versioning#conventional commits#specification#commits
One-click install
npx skills add https://github.com/Paxeer-Network/Sidiora-Perpetual-Protocol --skill specification-paxeer-network
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specification
Source: https://github.com/Paxeer-Network/Sidiora-Perpetual-Protocol/tree/main/.windsurf/skills/writing-git-commits/specification
Command: npx skills add https://github.com/Paxeer-Network/Sidiora-Perpetual-Protocol --skill specification-paxeer-network

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive and formal specification for Conventional Commits, ensuring clear, consistent, and machine-readable commit messages.

Core Features & Use Cases

  • Standardized Commit Format: Enforces a structured format for commit types, scopes, descriptions, bodies, and footers.
  • Automated Changelog Generation: Enables tools to automatically generate changelogs based on commit message types.
  • Semantic Versioning: Facilitates automatic determination of semantic version bumps (PATCH, MINOR, MAJOR) based on commit content.
  • Use Case: A development team can use this specification to ensure all their Git commits adhere to a standard, making the project history understandable and enabling automated release processes.

Quick Start

Review the formal grammar rules for Conventional Commits.

Frequently Asked Questions about specification

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

FAQPage Schema
What are conventional commits and how do they structure git messages?▼

Conventional commits provide a formal specification for structuring git messages using defined types, scopes, descriptions, bodies, and footers to ensure clear, machine-readable project history.

How do conventional commits determine semantic versioning bumps?▼

Conventional commits facilitate automatic semantic versioning determination by mapping specific commit types to PATCH, MINOR, or MAJOR version bumps based on the structured message content and breaking change indicators.

Can I automatically generate a changelog from conventional commit messages?▼

Yes, conventional commits enable automated changelog generation by allowing tools to parse the standardized commit types and descriptions, translating them directly into structured release notes.

How do I format breaking changes in a conventional commit message?▼

Breaking changes in conventional commits are formatted using a specific footer or an exclamation mark in the commit type header, formally detailing the change to trigger automated major version bumps.

Does the conventional commits specification require specific tools to enforce its rules?▼

The conventional commits specification provides a formal grammar and rules for commit message structure, which can be adopted by a development team to standardize git history without mandating specific tools.

Related Skills

Explore More Software Engineering Skills→
realsigridjinrealsigridjin
20

git-master

Create atomic Git commits with conventional formatting and manage repository history.

Community
Intermediate
FaysilAlshareefFaysilAlshareef
4

changelog-gen

Generate changelogs from git commits using Conventional Commits and Keep a Changelog formats.

Community
Intermediate
fiftynotaififtynotai
10

release

Generate changelogs and semantic version bumps from git commit history.

Community
Intermediate
RoxabiRoxabi
9

release-setup

Configure commit standards and release automation tools for Node, Bun, Deno, or Python projects.

Official
Advanced