skills.rest
simple-platform
simple-platformOFFICIAL
Explore all skills by this author →
GitHub

semantic-commits

Guide commit message writing using the Conventional Commits specification.

1|1|Updated Jan 4, 2026
Search Tags:#git#changelog#developer tools#versioning#conventional commits#commits
One-click install
npx skills add https://github.com/simple-platform/simple-tools --skill semantic-commits
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: semantic-commits
Source: https://github.com/simple-platform/simple-tools/tree/main/tools/simple-cli/internal/scaffold/templates/agent/skills/semantic-commits
Command: npx skills add https://github.com/simple-platform/simple-tools --skill semantic-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers write clear, consistent, and machine-readable commit messages, which is crucial for automated changelog generation and version bumping.

Core Features & Use Cases

  • Conventional Commits: Enforces a standard format (type(scope): description).
  • Automated Versioning: Enables tools to automatically determine Semantic Versioning (SemVer) bumps based on commit types (feat, fix).
  • Use Case: Ensure all team commits adhere to a standard, making it easy to generate release notes and track changes across the project.

Quick Start

Follow the guidelines in this skill to write a commit message for a new feature.

Frequently Asked Questions about semantic-commits

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

FAQPage Schema
How do I write conventional commit messages for automated changelog generation?▼

To write conventional commit messages, follow the standard format of type(scope): description. This structure defines commit types and scopes to generate automated changelogs and determine semantic versioning bumps.

What is the standard format for a git commit message to support semantic versioning?▼

The standard format for semantic versioning commits is type(scope): description. Using specific types like feat for features and fix for bug fixes allows automated tools to determine the correct version bump.

How do I structure commit messages for feature additions and bug fixes?▼

Structure commit messages for feature additions and bug fixes using the type(scope): description format. Prefix features with feat and bug fixes with fix to clearly categorize project changes.

Can I use conventional commits for documentation updates and refactoring?▼

Yes, conventional commits support documentation updates and refactoring by defining specific commit types. This standardizes messages across all development activities for clear project tracking.

Why do I need standardized commit messages for my development team?▼

Standardized commit messages ensure all team commits adhere to a machine-readable format. This consistency makes it easy to generate release notes, track changes, and automate versioning.

Related Skills

Explore More Software Engineering Skills→
d0whc3rd0whc3r
2

speckit-git-initialize

Initialize a Git repository and create an initial commit.

Community
Intermediate
FaysilAlshareefFaysilAlshareef
4

changelog-gen

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

Community
Intermediate
dennisonbertramdennisonbertram
1

changelog-gen

Generate release notes from Git history using Conventional Commits and git-cliff.

Community
Advanced
Tonybleything76Tonybleything76

Changelog Generator

Generate changelog entries from Git commit history using Conventional Commits.

Community
Advanced