--- name: conventional-gitmoji description: > Commit changes using the Conventional Commits spec with extended (Angular) types, prefixed with a gitmoji. Use automatically whenever the user asks you to commit — "commit", "commit this", "commit the changes", "write a commit message", "git commit" — or when you finish a piece of work and staged changes need committing. Produces messages like "✨ feat(auth): add login endpoint", stages related files, and runs git commit for you. --- # Conventional Commits + Gitmoji Commit the current work with a message that follows [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/), uses one of the **nine extended types** below, and carries a [gitmoji](https://github.com/carloscuesta/gitmoji) so the intent reads at a glance. You run the commit yourself; you don't just hand the user a message. ## Workflow 1. **Inspect.** Run `git status` and `git diff --staged` (also `git diff` for unstaged work). Read the whole change before you pick a type. 2. **Stage.** Stage the files that belong to one logical change: `git add `. Prefer targeted adds over `git add -A` so unrelated edits don't get swept into the commit. 3. **Pick exactly one type** from the table below. No other types. 4. **Pick a scope** (optional): the code area affected, lowercase kebab-case — `auth`, `api`, `parser`, `npm`, `scheduler`. 5. **Write the subject.** Imperative mood, lowercase, no trailing period, subject ≤ 72 chars (aim ≤ 50). 6. **Add a body** when the "why" isn't obvious (see Rules). 7. **Run `git commit`** with the message. ## Format ``` ():