skills.rest
antoncuranz
antoncuranzCOMMUNITY
Explore all skills by this author →
GitHub

conventional-commit

Generates conventional commit messages following the Conventional Commits specification.

Updated Mar 31, 2026
Search Tags:#git#changelog#conventional commits#semantic versioning#commit message#branch naming
One-click install
npx skills add https://github.com/antoncuranz/opencode-config --skill conventional-commit-antoncuranz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conventional-commit
Source: https://github.com/antoncuranz/opencode-config/tree/main/opencode/skills/conventional-commit
Command: npx skills add https://github.com/antoncuranz/opencode-config --skill conventional-commit-antoncuranz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, well-structured git commit messages is hard to enforce across a team, leading to messy history that breaks changelog generation and semantic versioning automation. ## Core Features & Use Cases - Standardized Commit Format: Produces messages in the <type>(<scope>): <subject> structure with proper body and footer sections. - Branch Discipline: Checks the current git branch and guides creation of typed feature branches like feat/add-user-auth before committing. - Breaking Change Handling: Formats breaking changes with ! markers and BREAKING CHANGE: footers that map to semantic versioning. - Use Case: After staging changes to an API endpoint, ask for a commit message and receive a properly scoped message like fix(api): Handle null response in user endpoint with an explanatory body. ## Quick Start Ask the assistant to commit the current staged changes using a conventional commit message.

Frequently Asked Questions about conventional-commit

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

FAQPage Schema
How do I write a conventional commit message?▼

Use the format `<type>(<scope>): <subject>` where type is one of feat, fix, docs, refactor, test, chore, and similar. Write the subject in imperative present tense, capitalize the first letter, omit the trailing period, and keep it under 70 characters.

What commit types are allowed in Conventional Commits?▼

The specification supports fix and feat as core types, plus build, chore, ci, deps, docs, perf, refactor, revert, style, and test from the Angular convention. Each type communicates intent, with fix mapping to PATCH and feat to MINOR in semantic versioning.

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

Append an exclamation mark after the type or scope, such as `feat(api)!: Remove deprecated v1 endpoints`, and add a `BREAKING CHANGE:` footer describing the impact. This correlates with a MAJOR version bump in semantic versioning.

Should I commit directly on the main branch?▼

No, check your current branch with `git branch --show-current` first. If you are on main or master, create a typed branch like `feat/add-user-auth` or `fix/null-pointer-error` before committing your changes.

What are the limits of conventional commit formatting?▼

All lines must stay under 100 characters and subjects under 70 characters. The format structures message text only; it does not enforce code quality, run tests, or validate that the described change matches the actual diff.

Related Skills

Explore More Software Engineering Skills→
jvm-skillsjvm-skills
135

commit

Group unstaged Git changes into logical commits with concise messages.

Official
Intermediate
edfentonedfenton
3

shared-changelog

Generate CHANGELOG.md from Git history using conventional commits.

Community
Advanced
diriendirien
19

commitlint

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

Community
Intermediate
l3ochol3ocho

changelog-format

Parse Conventional Commits and Keep a Changelog formats to generate release notes.

Community
Intermediate