--- name: commit type: workflow description: "Creates a well-formed git commit following conventional commit format with type, scope, and descriptive message. Use when the user is ready to commit changes or mentions conventional commits." context: fork agent: lead-programmer effort: 1 allowed-tools: Read, Glob, Grep, Write, Bash argument-hint: "[commit message or empty for auto-generate]" user-invocable: true when_to_use: "When creating git commits or asked to save/commit changes" --- # Conventional Commit Messages Follow these conventions when creating commits for this project. ## Prerequisites Before committing, always check the current branch: ```bash git branch --show-current ``` **If you're on `main` or `master`, confirm with the user before committing directly** — it is usually better to commit on a feature branch. Do not create a branch without user confirmation. Before claiming the change is ready to commit, use `verification-before-completion`: - Identify the exact readiness claim for the commit. - Run the relevant project checks, or state exactly why they cannot be run. - Inspect `git diff --stat` / changed files so the commit scope is known. - Do not say "ready to commit" if verification is partial or failed. ## Format ``` ():