Skip to content

windmill-labs/webmux / .claude/skills/commit

commit

Verified

Create 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

  1. Analyze changes: Run git status and git diff to understand what was modified
  2. Stage only modified files: Add files individually by name. NEVER use git add -A or git add .
  3. Write commit message: Follow the conventional commit format as a single line

Conventional Commit Format

<type>: <description>

Types

  • feat: New feature or capability
  • fix: Bug fix
  • refactor: Code change that neither fixes a bug nor adds a feature
  • docs: Documentation only changes
  • style: Formatting, missing semicolons, etc (no code change)
  • test: Adding or correcting tests
  • chore: Maintenance tasks, dependency updates, etc
  • perf: 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

  1. Run git status to see all changes
  2. Run git diff to understand the changes in detail
  3. Run git log --oneline -5 to see recent commit style
  4. Stage ONLY the modified/relevant files: git add <file1> <file2> ...
  5. Create the commit with conventional format:
    git commit -m "<type>: <description>
    
    Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>"
    
  6. Run git status to verify the commit succeeded
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 implementationStars: 318kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 318kUpdated Claude CodeCodexVerifiedInstall
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 fallbackStars: 318kUpdated Claude CodeCodexVerifiedInstall
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 alwaysStars: 318kUpdated Claude CodeCodexVerifiedInstall