aboutsummaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authornsfisis <nsfisis@gmail.com>2026-02-17 20:45:52 +0900
committernsfisis <nsfisis@gmail.com>2026-02-17 20:45:52 +0900
commit573da3ea47dcbe708470b88b506594c1d80ec78f (patch)
tree6c25592701295440dede639efa1de73994e9a041
parent3bfe4f1b8fc1668a8291072f495c3ed0fe507a66 (diff)
downloaddotfiles-573da3ea47dcbe708470b88b506594c1d80ec78f.tar.gz
dotfiles-573da3ea47dcbe708470b88b506594c1d80ec78f.tar.zst
dotfiles-573da3ea47dcbe708470b88b506594c1d80ec78f.zip
claude: update /conventional-commit
-rw-r--r--.config/claude/skills/conventional-commit/SKILL.md1
1 files changed, 1 insertions, 0 deletions
diff --git a/.config/claude/skills/conventional-commit/SKILL.md b/.config/claude/skills/conventional-commit/SKILL.md
index 578a916..d96c71f 100644
--- a/.config/claude/skills/conventional-commit/SKILL.md
+++ b/.config/claude/skills/conventional-commit/SKILL.md
@@ -15,6 +15,7 @@ allowed-tools: Bash(git add:*), Bash(git diff:*), Bash(git status:*), Bash(git c
1. Check the git status and changes.
2. Analyze the changes and draft a commit message following Conventional Commits format:
- Types: feat, fix, refactor, test, docs, chore, style, perf, ci, build
+ - **refactor**: Only for internal code improvements that do NOT change externally observable behavior. If the change alters config, adds functionality, fixes a bug, or changes any visible output, it is NOT a refactor. When in doubt, prefer feat, fix, chore, or another more accurate type.
- Format: `<type>(<scope>): <description>`
- Keep the first line under 72 characters
- Add a blank line and body if more context is needed