conventional-commit
Installation
Summary
Structured commit message format following the Conventional Commits specification.
- Defines 12 commit types (feat, fix, refactor, docs, test, chore, ci, build, perf, style, deps, revert) with clear purposes and semantic versioning correlation
- Enforces a required header format with optional scope and body, all lines under 100 characters, subject line capped at 70 characters
- Includes guidelines for imperative present-tense language, body content explaining what and why, and support for BREAKING CHANGE footers to signal major version bumps
- Provides branch naming conventions matching commit types and examples covering simple fixes, features with scope, refactors, breaking changes, and reverts
SKILL.md
Conventional Commit Messages
Follow these conventions when creating commits.
Prerequisites
Before committing, ensure you're working on a feature branch, not the main branch.
# Check current branch
git branch --show-current
If you're on main or master, create a new branch first:
# Create and switch to a new branch
git checkout -b <type>/<short-description>
Related skills
More from marcelorodrigo/agent-skills
filament-pro
Build Laravel admin panels with Filament v5. Use for creating resources, forms, tables, widgets, and testing admin interfaces with Livewire v4.
528create-pr
Create Pull Requests following best conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review.
233spring-boot-testing
Expert Spring Boot 4 testing specialist that selects the best Spring Boot testing techniques for your situation with Junit 6 and AssertJ.
123phpstan-fixer
|
59