conventional-commitslisted

# Conventional Commits Standard This skill provides comprehensive knowledge about the Conventional Commits specification (v1.0.0) for writing structured, machine-readable commit messages that drive automated versioning and changelog generation. ## Overview Conventional Commits structures commit messages as `type(scope): description` to create an explicit commit history that enables automated tooling for versioning, changelog generation, and release management. ## Commit Message Format ``` <type>[optional scope]: <description> [optional body] [optional footer(s)] ``` ## Types and Their Versioning Impact | Type | Purpose | SemVer Impact | |------|---------|---------------| | `feat` | New feature | MINOR bump | | `fix` | Bug fix | PATCH bump | | `docs` | Documentation only | No bump | | `style` | Formatting, no logic change | No bump | | `refactor` | Code change that neither fixes nor adds | No bump | | `perf` | Performance improvement | No bump (or PATCH) | | `test` | Adding or correcting tests | No bump | | `build` | Build system or external dependencies | No bump | | `ci` | CI configuration changes | No bump | | `chore` | Other changes not modifying src/test | No bump | | `revert` | Reverts a previous commit | Depends on reverted type | ## Breaking Changes Two ways to indicate a breaking change (triggers MAJOR version bump): 1. **Footer notation**: `BREAKING CHANGE: description` in the commit footer 2. **Type suffix**: Append `!` after type/scope — `feat!: remove