dev:commit

Compatibility: If AskUserQuestion is unavailable, present options as a numbered list and wait for the user's reply. If Task is unavailable, run parallel steps sequentially. The context: fork and agent: frontmatter fields are Claude Code-specific — on OpenCode and VS Code Copilot they are ignored and the skill runs inline using the current model.

Create a git commit following conventional commit standards with a professional, concise message.

Rules

Choosing the right type

1. Does it add new functionality users can use? → feat
2. Does it fix broken behavior? → fix
3. Does it change existing behavior (breaking)? → feat! or fix!
4. Does it only improve code structure? → refactor
5. Does it only update documentation? → docs
6. Does it only affect tests? → test
7. Does it only affect build/CI? → chore

Bump behavior is determined by your project's release config (.releaserc.*, commitizen.config.*, [tool.commitizen]). Do not predict version bumps — check those files if needed.

Never commit secrets