BuddiesOfBudgie/docs / .claude/skills/commit
commit
VerifiedStage and commit changes using Conventional Commits
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.9 KB |
SKILL.md
View on GitHub---
name: commit
description: Stage and commit changes using Conventional Commits
disable-model-invocation: false
allowed-tools: Bash(git *)
---
Create a git commit for the current changes following the Conventional Commits specification.
## Steps
1. Run these commands in parallel to understand the current state:
- `git status` to see all changed and untracked files
- `git diff` to see unstaged changes
- `git diff --cached` to see already-staged changes
- `git log --oneline -5` to see recent commit style
2. Analyze the changes and determine:
- Which files should be staged (skip files that likely contain secrets like `.env`, credentials, etc.)
- The appropriate Conventional Commit type and scope
- A concise description of the change
3. Stage the relevant files by name (do NOT use `git add -A` or `git add .`)
4. Determine attribution - analyze the conversation context:
- **Did Claude write or modify code/content** (generate implementations, write documentation, create components)? → Add `Assisted-by: Claude:<model-id>` trailer
- **Did Claude only perform mechanical tasks** (committing, formatting, running commands) or did the human make all changes? → NO trailer
- Never use `Co-Authored-By`
5. Craft the commit message using the types, scopes, and rules defined in [CONTRIBUTING.md](CONTRIBUTING.md#conventional-commits). Additional skill-specific rules:
- Scope is optional but encouraged - use the most relevant area
- If changes span multiple concerns, prefer a single commit with a clear summary over being overly granular
- Always pass the commit message via a HEREDOC:
```bash
git commit -s -m "$(cat <<'EOF'
type(scope): description
Optional body.
Assisted-by: Claude:<model-id>
EOF
)"
```
6. After committing, run `git status` to verify success.
## Arguments
If `$ARGUMENTS` is provided, use it as guidance for the commit message or scope.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |