Write clear, conventional Git commit messages following a consistent structure and ruleset
Help write well-structured Git commit messages following the Conventional Commits specification.
<type>(<optional scope>): <description>
[optional body]
Use exactly one of: build, chore, ci, docs, feat, fix, perf,
refactor, style, test
feat — adds a new featurefix — fixes a bugadd, fix, update, remove, rename- Good subject lines:
feat(opencode): add declarative skills support
fix(zsh): correct PATH ordering for homebrew on darwin
chore(deps): update flake inputs
refactor(nixvim): extract keymap definitions into separate file
Good commit with body:
feat(opencode): add declarative skills support
- Add skills.enable toggle for built-in skills bundled with the config
- Add skills.extraSkillsDirs for external skill directories
- Deploy each skill to ~/.config/opencode/skills/<name>/SKILL.md
- Use last-writer-wins on name collision to allow overrides
Body-less commit (body would add no value):
chore(deps): update flake inputs