code-commit

# Conventional Commit Skill Generate and validate commit messages following the [Conventional Commits](https://www.conventionalcommits.org/) specification. ## Conventional Commit Format ``` <type>(<scope>): <subject> [optional body] [optional footer(s)] ``` ### Types | Type | Description | |------|-------------| | `feat` | New feature | | `fix` | Bug fix | | `docs` | Documentation only | | `style` | Code style (formatting, semicolons, etc.) | | `refactor` | Code change that neither fixes nor adds | | `test` | Adding or updating tests | | `chore` | Build, tooling, dependencies | | `perf` | Performance improvement | | `ci` | CI configuration changes | | `build` | Build system or dependencies | | `revert` | Reverting a previous commit | ### Rules - **Subject**: Short description, imperative mood, lowercase, no period at end - **Scope**: Optional, lowercase, describes what was changed (e.g., `auth`, `api`, `ui`) - **Breaking changes**: Add `!` after type/scope: `feat(auth)!: change API` - **Footer**: For breaking changes (`BREAKING CHANGE:`) or issue references (`Closes #123`) ## Operations ### 1. Generate Commit from Diff When user wants to commit changes: 1. Run `git status` to see changed files 2. Run `git diff --staged` for staged changes 3. Analyze what changed to determine: - **Type**: Which type best describes the changes? - **Scope**: What area was affected? (optional) - **Subject**: What was done? (imperative: "add" not "added") 4. Create a conventi...