maji-commitlisted

# maji-commit — Auto-generate Commit Messages A skill that reads your staged or unstaged git diff and writes a clean commit message in conventional commits format. No manual typing, no overthinking the wording. --- ## When to Use Type `maji-commit` (or `commit message?`) after running `git diff` or `git diff --staged`. Claude reads the diff, infers the change, outputs a commit message you can copy-paste. --- ## Input → Output **Input:** Current staged/unstaged diff in the working directory. **Output:** A single commit message string in conventional commits format. ``` <type>(<scope>): <subject> [optional body — only if change is non-obvious] ``` --- ## Format Rules ### Type (required) | Type | When to use | |---|---| | `feat` | New feature or capability | | `fix` | Bug fix | | `refactor` | Code restructure, no behaviour change | | `chore` | Tooling, deps, config | | `docs` | Documentation only | | `style` | Formatting, no logic change | | `test` | Tests added or changed | | `perf` | Performance improvement | | `build` | Build system, packaging | | `ci` | CI/CD changes | ### Scope (optional) A noun describing the affected area: `auth`, `api`, `ui`, `db`, etc. Use when it adds clarity. Skip when scope is obvious or change spans multiple areas. ### Subject - Imperative mood ("add", "fix", "remove" — not "added", "fixes", "removed") - Lowercase first letter - No period at end - ≤ 72 characters - Describe **what changed**, not how ### Body (only when needed) Sk