oma-commit

# Commit Skill - Conventional Commits ## When to use - When user requests "commit this", "commit", "save changes" - When `/commit` command is invoked ## Configuration Project-specific settings: `.agents/skills/commit/config/commit-config.yaml` ## Commit Types | Type | Description | Branch Prefix | |------|-------------|---------------| | feat | New feature | feature/ | | fix | Bug fix | fix/ | | refactor | Code improvement | refactor/ | | docs | Documentation changes | docs/ | | test | Test additions/modifications | test/ | | chore | Build, configuration, etc. | chore/ | | style | Code style changes | style/ | | perf | Performance improvements | perf/ | ## Commit Format ``` <type>(<scope>): <description> [optional body] Co-Authored-By: First Fluke <our.first.fluke@gmail.com> ``` ## Workflow ### Step 1: Analyze Changes ```bash git status git diff --staged git log --oneline -5 ``` ### Step 1.5: Split by Feature (if needed) If changed files span multiple features/domains, **split commits by feature**. **Split criteria:** - Different scopes (e.g., workflows vs skills vs docs) - Different types (e.g., feat vs fix vs docs) - Logically independent changes **Example:** ``` # Changed files: .agents/workflows/*.md (7 files) → fix(workflows): ... .agents/skills/**/*.md (4 files) → fix(skills): ... USAGE.md, USAGE-ko.md → docs: ... # Split into 3 commits ``` **Do NOT split when:** - All changes belong to a single feature - Few files changed (5 or fewer)...