commit

name	commit
description	Generate clean, professional Git commit messages from actual code changes, diffs, staged changes, or user-provided change summaries. Use when Codex is asked to write, improve, choose, or suggest a commit message, especially semantic commit messages.

Commit

Workflow

1. Inspect the actual change when possible using git status, git diff, and git diff --cached.
2. Identify the main purpose of the change.
3. Pick the best semantic commit type.
4. Write one short imperative-present summary that describes what changed.
5. Return only the commit message unless the user asks for alternatives or explanation.

Do not make a commit unless the user explicitly asks for that.

Message Rules

• Use semantic commit format: type: short imperative summary.
• Use imperative present tense: add, fix, update, remove, refactor.
• Keep the message short, clear, specific, and professional.
• Describe the actual change, not the process of changing it.
• Avoid vague wording such as update stuff, fix things, or added changes.
• Avoid emotional, joking, frustrated, random, or unprofessional wording.
• If the change cannot be inspected and no change summary is available, ask for the diff or summary instead of inventing a message.

Semantic Types

• feat: add a new feature
• fix: fix a bug
• refactor: change code structure without changing behavior
• docs: update documentation
• style: formatting or styling only
• test: add or update tests
• chore: maintenance work
• perf: improve performance
• build: update build system or dependencies
• ci: update CI/CD configuration

Examples

Good:

feat: add user profile page
fix: prevent checkout crash on empty cart
refactor: simplify auth middleware
docs: update setup instructions
test: add login validation tests
chore: update dependencies

Bad:

added more changes
fixed stuff
get working already
finally done
random fixes