skills.rest
knoopx
knoopxCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

conventional-commits

Enforce and format git commit messages according to the Conventional Commits spec.

68|1|Updated Jan 14, 2026
Search Tags:#git#changelog#lint#semantic-versioning#conventional-commits#commit-messages
One-click install
npx skills add https://github.com/knoopx/pi --skill conventional-commits-knoopx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conventional-commits
Source: https://github.com/knoopx/pi/tree/main/agent/skills/conventional-commits
Command: npx skills add https://github.com/knoopx/pi --skill conventional-commits-knoopx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams enforce a consistent commit message format across the repository, enabling reliable changelogs and semantic versioning.

Core Features & Use Cases

  • Enforce and draft Conventional Commits (type(scope): subject) for new commits.
  • Support breaking change indicators and proper footers for issue references.
  • Use in PR titles and release notes to generate changelogs and automate version bumps.

Quick Start

Draft a Conventional Commits message: feat(auth): add passwordless login

Frequently Asked Questions about conventional-commits

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

FAQPage Schema
What are conventional commits and why use them in git?▼

Conventional commits standardize git commit messages using a type and scope format to enable automated changelog generation and semantic versioning. This structured format ensures consistent repository history and allows tooling to automatically determine version bumps.

How do I format a git commit message for semantic versioning?▼

To format a git commit message for semantic versioning, use the conventional commits structure: type(scope): subject. This Skill enforces proper header, body, and footer sections, including breaking-change markers and allowed types, to support reliable automated versioning.

Can I use conventional commits for PR titles and release notes?▼

Yes, conventional commits can be applied to PR titles and release notes. Using this standardized format in pull requests allows teams to automatically generate changelogs and automate version bumps directly from the merged history.

How do I indicate a breaking change in a commit message?▼

To indicate a breaking change in a commit message, this Skill enforces proper breaking-change markers within the commit structure. It ensures these markers are correctly followed in the header or footer sections to trigger major semantic version bumps.

Does this conventional commits skill require any dependencies?▼

No, this conventional commits skill has no external dependencies. It operates independently to enforce and format your commit messages according to the specification without requiring additional linting tools or frameworks.

Related Skills

Explore More Software Engineering Skills→
mhaldermhalder
2

commit

Generate conventional commit messages with type(scope): description format.

Community
Basic
FaysilAlshareefFaysilAlshareef
4

changelog-gen

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

Community
Intermediate
avvaleavvale

conventional-commits

Validate commit messages against the Conventional Commits specification.

Official
Basic
FullFranFullFran
1

commit-convention

Enforce Conventional Commits format for git commit messages.

Community
Intermediate