dotfiles/dot_claude/skills/commit/SKILL.md

name, description, disable-model-invocation, effort, model, allowed-tools

name	description	disable-model-invocation	effort	model	allowed-tools
commit	Create git commits with well-formatted conventional commit messages.	true	low	haiku	Glob Grep Read TodoWrite TaskCreate TaskUpdate TaskList

Commit

Create commits with well-formatted conventional commit messages.

Process

1. Check for changes (git status). If something is staged, consider only staged changes. Otherwise, review and stage appropriate files.
2. Determine the commit type (e.g. feat, fix, docs, refactor, ...).
3. Generate a descriptive commit message using conventional commit standards. Include scope if applicable: type(scope): description.
4. Add a body for complex changes explaining the why.
5. Execute the commit.

Best Practices

• Keep commits atomic and focused
• Write in imperative style ("Add feature" not "Added feature")
• Explain why, not just what
• Reference issues/PRs when relevant
• Split unrelated changes into separate commits
• Do not add Claude Code as co-author to the commit