skills.rest
kobogithub
kobogithubCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

standard-commits

Enforce Conventional Commits and semantic versioning for Git projects.

Updated Feb 12, 2026
Search Tags:#git#ci/cd#code review#conventional commits#semantic versioning#branching strategy
One-click install
npx skills add https://github.com/kobogithub/knowledge --skill standard-commits
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: standard-commits
Source: https://github.com/kobogithub/knowledge/tree/main/skills/standard-commits
Command: npx skills add https://github.com/kobogithub/knowledge --skill standard-commits

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill establishes and enforces consistent standards for commit messages, versioning, and Git branching across development teams, preventing chaos and improving code quality.

Core Features & Use Cases

  • Conventional Commits: Enforces a structured format for commit messages (type(scope): message).
  • Semantic Versioning: Automates version bumping (MAJOR, MINOR, PATCH) based on commit types.
  • Git Branching Strategy: Defines clear workflows for feature development, hotfixes, and releases.
  • Use Case: Ensure all team members adhere to the same commit message format, making it easy to understand changes and automatically generate release notes and version numbers.

Quick Start

Follow the Conventional Commits format for all your Git commits.

Frequently Asked Questions about standard-commits

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

FAQPage Schema
How do I enforce conventional commits for Git commit messages?▼

You enforce conventional commits by mandating a structured format (`type(scope): message`) for all Git commit messages. This Skill guides agents on commit rules to maintain consistent development practices across your repository.

What is the best way to automate semantic versioning based on commit types?▼

Automating semantic versioning based on commit types is achieved by mapping structured commit messages to version bumps (MAJOR, MINOR, PATCH). This establishes a semantic versioning strategy to automatically generate project releases.

How do I set up a Git branching strategy for feature development and hotfixes?▼

You set up a Git branching strategy by implementing a structured model with production, development, epic, and agent work branches. This model defines clear workflows for feature development, hotfixes, and releases.

Does this branching model support CI/CD integration and PR workflows?▼

Yes, this branching model supports CI/CD integration and PR workflows. It guides agents on commit rules and pull request workflows to maintain consistent software development practices within your pipeline.

Why use semantic versioning for project releases?▼

You use semantic versioning for project releases to automatically bump version numbers (MAJOR, MINOR, PATCH) based on commit types. This prevents chaos and makes it easy to automatically generate release notes.

Related Skills

Explore More Software Engineering Skills→
diriendirien
19

commitlint

Validate commit messages against the Conventional Commits specification in Node.js git environments.

Community
Intermediate
mvandermeulenmvandermeulen
2

changelog-automation

Generate project changelogs and release notes from Conventional Commits history.

Community
Advanced
simotasimota
68

Guardian

Analyze Git changes, commits, and branches for code quality insights.

Community
Advanced
mcj-codermcj-coder
1

branching-strategy-and-conventions

Configure Git branching strategies, Conventional Commits, and merge rules.

Community
Advanced