← スキル一覧に戻る

commit
by arowinski
Configuration files
⭐ 0🍴 2📅 2025年11月29日
SKILL.md
name: commit description: Creates commits with generated messages following project conventions. Use when asked to commit changes or create a commit. allowed-tools: Bash(git status:), Bash(git diff:), Bash(git add:), Bash(git commit:), Read, Glob
Commit
Overview
Automates commit creation by analyzing changes, generating appropriate commit messages following project conventions, and creating commits with proper staging.
Workflow
Step 1: Check Status
- Run
git statusto see modified and untracked files - Run
git diffto see unstaged changes - Run
git diff --stagedto see staged changes - If no changes to commit, inform user and stop
Step 2: Analyze Changes
- Identify the primary purpose - what's the main change?
- New feature? Which one?
- Bug fix? What bug?
- Refactoring? Of what?
- Configuration change? What aspect?
- Determine type: feature, fix, refactor, chore, docs, etc.
- Identify scope: which files/modules are affected
Step 3: Generate Commit Message
Follow these requirements:
Message structure:
- First line: Concise summary of primary change
- Use imperative mood ("Add feature", "Fix bug", NOT "Added" or "Adds")
- Keep it focused on the single most important change
- Max 80 characters
- Blank line
- Body (if multiple significant changes):
- Bullet points for additional changes
- Focus only on most important changes
Content guidelines:
- Use third person ("This adds..." NOT "I added...")
- Focus on WHAT and WHY, not HOW
- Don't mention tests unless they're a significant part of the commit (e.g., new testing framework, major test infrastructure changes)
- Use backticks for code references (variables, methods, classes, file names)
Step 4: Stage and Commit
-
Stage relevant files with
git add:- Include modified files that are part of the change
- Include new files if appropriate
- Don't stage files that likely contain secrets (.env, credentials.json, etc.)
- Warn user if trying to commit secret files
-
Create commit with generated message:
- NEVER add Claude footer or "Generated with Claude Code" links
- NEVER add "Co-Authored-By: Claude" lines
- Use heredoc for proper formatting:
git commit -m "$(cat <<'EOF' Commit message here EOF )" -
Run
git statusafter commit to verify success
スコア
総合スコア
50/100
リポジトリの品質指標に基づく評価
✓SKILL.md
SKILL.mdファイルが含まれている
+20
○LICENSE
ライセンスが設定されている
0/10
○説明文
100文字以上の説明がある
0/10
○人気
GitHub Stars 100以上
0/15
○最近の活動
3ヶ月以内に更新がある
0/10
○フォーク
10回以上フォークされている
0/5
✓Issue管理
オープンIssueが50未満
+5
✓言語
プログラミング言語が設定されている
+5
○タグ
1つ以上のタグが設定されている
0/5
レビュー
💬
レビュー機能は近日公開予定です