Generate commit messages following the Conventional Commits 1.0.0 specification.
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
When the user asks to commit changes:
Analyze the changes by running:
git status to see all modified/added/deleted filesgit diff --staged to see staged changesgit diff to see unstaged changesgit log -5 --oneline to match the repository's commit styleDetermine the commit type (REQUIRED):
| Type | Description | SemVer |
|---|---|---|
feat | New feature | MINOR |
fix | Bug fix | PATCH |
docs | Documentation only | - |
style | Formatting, no code change | - |
refactor | Code change, no feature/fix | - |
perf | Performance improvement | - |
test |
Identify breaking changes:
Write the commit message:
Stage and commit:
git addgit status after to confirm successfeat, fix, etc.)- instead of spaces (except BREAKING CHANGE)BREAKING CHANGE MUST be uppercaseCo-Authored-By: Claude footersfeat: allow provided config object to extend other configs
BREAKING CHANGE: `extends` key in config file is now used for extending other config files
!feat(api)!: send an email to the customer when a product is shipped
chore!: drop support for Node 6
BREAKING CHANGE: use JavaScript features not available in Node 6.
docs: correct spelling of CHANGELOG
feat(lang): add Polish language
fix: prevent racing of requests
Introduce a request id and a reference to latest request. Dismiss
incoming responses other than from latest request.
Remove timeouts which were used to mitigate the racing issue but are
obsolete now.
Reviewed-by: Z
Refs: #123
revert: let us never again speak of the noodle incident
Refs: 676104e, a215868
Footers follow git trailer format:
Token: value or Token #valueRefs:, Closes:, Reviewed-by:, Co-authored-by:BREAKING CHANGE: description for breaking changesIf changes are complex or ambiguous, ask the user:
| Adding/updating tests |
| - |
build | Build system or dependencies | - |
ci | CI configuration | - |
chore | Other changes | - |
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).