# conventional-commits

> Enforces conventional commit message format for all git commits

- Author: chaz8080
- Repository: chaz8081/positive-vibes
- Version: 20260208220952
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-09
- Source: https://github.com/chaz8081/positive-vibes
- Web: https://mule.run/skillshub/@@chaz8081/positive-vibes~conventional-commits:20260208220952

---

---
name: conventional-commits
description: Enforces conventional commit message format for all git commits
version: "1.0"
author: positive-vibes
tags:
  - git
  - commits
  - standards
---

# Conventional Commits

Always use the Conventional Commits format for all commit messages.

## Format

```
<type>[optional scope]: <description>

[optional body]

[optional footer(s)]
```

## Types

- **feat**: A new feature
- **fix**: A bug fix
- **docs**: Documentation only changes
- **style**: Changes that do not affect the meaning of the code
- **refactor**: A code change that neither fixes a bug nor adds a feature
- **test**: Adding missing tests or correcting existing tests
- **chore**: Changes to the build process or auxiliary tools

## Rules

1. The commit message MUST start with a type
2. A scope MAY be provided after a type
3. A description MUST immediately follow the type/scope prefix
4. The description MUST be a short summary of the code changes
5. Breaking changes MUST be indicated by a `!` after the type/scope or by a `BREAKING CHANGE:` footer