By name: commit description: >- Generate and run a concise conventional commit for staged changes when the user explicitly asks to commit, create a git commit, or finish a staged change as a commit. Do not use for requests that only ask to draft, suggest, or review a commit message.
Commit
Create a concise, factual commit message from staged changes and run the commit only when the user explicitly asks to commit.
Workflow
- Confirm the user asked to actually commit, not only draft or suggest a message.
- Analyze only staged changes.
- If there are no staged changes, print
No staged changes to commitand stop. - Generate a commit message that follows the required format.
- Run
git commitwith that message. - Report the final committed message or the failure cause.
Rules
- Be fast; this task is not a long-running process.
- Never include unstaged or untracked changes in the commit analysis.
- Do not commit unless the user's request clearly asks to create a commit.
- On failure, do not retry, amend, stage files, or modify files unless the user asks.
- Commit format:
- Follow conventional commits:
[type]([scope]): [description]plus an optional body. - Scope is optional; if present, use modules or domains clearly defined in the project.
- Body is optional; if present, add one blank line after the subject and prefer bullet points.
- Description is imperative, has no trailing period or whitespace, and is no more than 50 characters.
- Use lowercase type and English only.
- Follow conventional commits:
Output
On success, print:
Commit successful
[committed message]
On failure, print:
Commit failed
[cause from the error output]