conventional-commit

# Conventional Commit Generate commit messages following the [Conventional Commits 1.0.0](https://www.conventionalcommits.org/) specification. ## Commit Message Structure ``` <type>[optional scope]: <description> [optional body] [optional footer(s)] ``` ## Instructions When the user asks to commit changes: 1. **Analyze the changes** by running: - `git status` to see all modified/added/deleted files - `git diff --staged` to see staged changes - `git diff` to see unstaged changes - `git log -5 --oneline` to match the repository's commit style 2. **Determine the commit type** (REQUIRED): | Type | Description | SemVer | |------|-------------|--------| | `feat` | New feature | MINOR | | `fix` | Bug fix | PATCH | | `docs` | Documentation only | - | | `style` | Formatting, no code change | - | | `refactor` | Code change, no feature/fix | - | | `perf` | Performance improvement | - | | `test` | Adding/updating tests | - | | `build` | Build system or dependencies | - | | `ci` | CI configuration | - | | `chore` | Other changes | - | 3. **Identify breaking changes**: - Append "!" after type/scope for breaking changes: "feat!:" or "feat(api)!:" - Add "BREAKING CHANGE:" footer for detailed explanation - Breaking changes trigger MAJOR version bump 4. **Write the commit message**: - Description MUST immediately follow the colon and space - Description is a short summary in imperative mood - Body MUST begin one blank...