Commit Message Convention

Generate Conventional Commits commit messages with predefined types and breaking change markers.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/mulatta/cast --skill commit-message-convention
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Commit Message Convention
Source: https://github.com/mulatta/cast/tree/main/.claude/skills/commit-convention
Command: npx skills add https://github.com/mulatta/cast --skill commit-message-convention

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of inconsistent and uninformative commit messages, which often lead to a messy project history, hinder collaboration, and complicate tasks like generating changelogs or tracking down specific changes.

Core Features & Use Cases

  • Standardized Commit Types: Utilize predefined types like feat, fix, docs, refactor, and chore to instantly convey the intent and impact of each change.
  • Breaking Change Identification: Clearly mark commits that introduce breaking changes, enabling automated semantic versioning and accurate release note generation.
  • Use Case: Automatically generate a comprehensive and accurate changelog for your project's next release. By ensuring all commits adhere to the Conventional Commits specification, you can transform release note creation from a manual chore into an automated, reliable process.

Quick Start

Help me write a commit message for a new feature that adds user authentication. The feature is called 'SecureAuth' and it's a breaking change because it modifies the existing login API.