skills.rest
maystudios
maystudiosCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit-conventions

Enforce conventional commit messages with type, scope, description, and Co-Authored-By line.

10|1|Updated Feb 24, 2026
Search Tags:#git#versioning#commit#style#lint#conventional-commit#co-author
One-click install
npx skills add https://github.com/maystudios/maxsimcli --skill commit-conventions-maystudios
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-conventions
Source: https://github.com/maystudios/maxsimcli/tree/main/templates/skills/commit-conventions
Command: npx skills add https://github.com/maystudios/maxsimcli --skill commit-conventions-maystudios

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conventional commit messages improve project history, changelog generation, and automated versioning by ensuring consistent, meaningful commits.

Core Features & Use Cases

  • Enforces a strict commit message format (type(scope): description) across the project.
  • Supports optional breaking-change indicator via type!(scope): description and Co-Authored-By attribution for AI-assisted commits.
  • Improves changelogs, releases, and traceability in collaborative workflows.

Quick Start

Format a new change using the conventional-commit syntax: type(scope): description.

Frequently Asked Questions about commit-conventions

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

FAQPage Schema
How do I enforce conventional commit messages in a collaborative git workflow?▼

To enforce conventional commit messages, apply a strict format of type(scope): description across your project. This standardizes project history and improves traceability in collaborative software development workflows and CI/CD pipelines.

How do I indicate a breaking change in a conventional commit format?▼

You indicate a breaking change in a conventional commit by using the type!(scope): description syntax. The exclamation mark explicitly flags the breaking change within the standardized commit message structure.

How do I attribute AI-assisted commits using conventional commit standards?▼

You attribute AI-assisted commits by appending a Co-Authored-By line to your standardized commit message. This maintains traceability for AI-assisted commits while adhering to the strict conventional-commit format.

Why use a strict conventional commit format for project changes?▼

Using a strict conventional commit format improves project history, automates changelog generation, and enables automated versioning. It ensures consistent, meaningful commits by enforcing a standardized structure across all project changes.

Does enforcing conventional commits work with CI/CD pipelines?▼

Enforcing conventional commits works directly with CI/CD pipelines by applying a strict commit message format. This standardization supports collaborative software development workflows and improves automated releases and changelog generation.

Related Skills

Explore More Software Engineering Skills→
ivyivy
9

commit

Stage intended files and write conventional, why-focused commit messages.

Community
Advanced
marquesfelipmarquesfelip

automated-versioning

Automate semantic version bumps from conventional commits in CI/CD pipelines.

Community
Advanced
voidrotvoidrot

changelog-automation

Generate changelogs and release notes from commit history and tags.

Community
Advanced
mhattingpetemhattingpete
657

git-pushing

Stage, commit, and push code changes with conventional commit messages.

Community
Basic