mirror of
https://github.com/dnlbauer/dotfiles.git
synced 2026-09-11 14:05:29 +00:00
feat: add claude config
This commit is contained in:
37
dot_claude/skills/commit/SKILL.md
Normal file
37
dot_claude/skills/commit/SKILL.md
Normal file
@@ -0,0 +1,37 @@
|
||||
---
|
||||
name: commit
|
||||
description: >-
|
||||
Create git commits with well-formatted conventional commit messages.
|
||||
disable-model-invocation: true
|
||||
effort: low
|
||||
model: haiku
|
||||
allowed-tools:
|
||||
- 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
|
||||
Reference in New Issue
Block a user