conventional-commit

Original：🇺🇸 English

Translated

Create conventional commit messages following best conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits specification.

2installs

Sourcemarcelorodrigo/agent-skills

Added on2026-02-04

NPX Install

npx skill4agent add marcelorodrigo/agent-skills conventional-commit

SKILL.md Content

View Translation Comparison →

Conventional Commit Messages

Follow these conventions when creating commits.

Prerequisites

Before committing, ensure you're working on a feature branch, not the main branch.

bash

# Check current branch
git branch --show-current

If you're on

main

or

master

, create a new branch first:

bash

# Create and switch to a new branch
git checkout -b <type>/<short-description>

Branch naming should follow the pattern:

<type>/<short-description>

where type matches the commit type (e.g.,

feat/add-user-auth

,

fix/null-pointer-error

,

refactor/extract-validation

).

Format

<type>(<scope>): <subject>

<body>

<footer>

The header is required. Scope is optional. All lines must stay under 100 characters.

Commit Types

Type	Purpose
`build`	Build system or CI changes
`chore`	Routine maintenance tasks
`ci`	Continuous integration configuration
`deps`	Dependency updates
`docs`	Documentation changes
`feat`	New feature
`fix`	Bug fix
`perf`	Performance improvement
`refactor`	Code refactoring (no behavior change)
`revert`	Revert a previous commit
`style`	Code style and formatting
`test`	Tests added, updated or improved

Subject Line Rules

Use imperative, present tense: "Add feature" not "Added feature"
Capitalize the first letter
No period at the end
Maximum 70 characters

Body Guidelines

Explain what and why, not how
Use imperative mood and present tense
Include motivation for the change
Contrast with previous behavior when relevant