windmill-labs/webmux / .claude/skills/commit
commit
VerifiedCreate a git commit with conventional commit format. MUST use anytime you want to commit changes.
Git Commit Skill
Create a focused, single-line commit following conventional commit conventions.
Instructions
- Analyze changes: Run
git statusandgit diffto understand what was modified - Stage only modified files: Add files individually by name. NEVER use
git add -Aorgit add . - Write commit message: Follow the conventional commit format as a single line
Conventional Commit Format
<type>: <description>
Types
feat: New feature or capabilityfix: Bug fixrefactor: Code change that neither fixes a bug nor adds a featuredocs: Documentation only changesstyle: Formatting, missing semicolons, etc (no code change)test: Adding or correcting testschore: Maintenance tasks, dependency updates, etcperf: Performance improvement
Rules
- Message MUST be a single line (no multi-line messages)
- Description should be lowercase, imperative mood ("add" not "added")
- No period at the end
- Keep under 72 characters total
Examples
feat: add token usage tracking for AI providers
fix: resolve null pointer in job executor
refactor: extract common validation logic
docs: update API endpoint documentation
chore: upgrade sqlx to 0.7
Execution Steps
- Run
git statusto see all changes - Run
git diffto understand the changes in detail - Run
git log --oneline -5to see recent commit style - Stage ONLY the modified/relevant files:
git add <file1> <file2> ... - Create the commit with conventional format:
git commit -m "<type>: <description> Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>" - Run
git statusto verify the commit succeeded
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: 318k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 318k | 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: 318k | 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: 318k | Updated | Claude CodeCodex | Verified | Install |