Overview

Commit Wizard automatically generates clear, conventional commit messages from your staged changes. It adheres to the conventional commits format and can include scope suggestions, breaking-change notes, and optional emojis to improve readability and tooling compatibility.

How This Skill Works

It analyzes the git diff of your staged changes to infer context and impact. It then formats the result as a conventional commit (for example, feat(scope): description) and appends optional details for breaking changes or changelog-friendly notes.

When to Use It

• Before committing new features to ensure a standardized message
• While fixing bugs to capture actionable history
• During refactors to document scope and impact
• When updating dependencies or performing chores
• Prior to opening a PR to align with team conventions

Quick Start

1. Step 1: Stage your changes in git (git add ...)
2. Step 2: Ask Claude to generate a commit message (e.g., 'Generate a commit message for my changes')
3. Step 3: Run git commit -m "<generated message>"

Best Practices

• Use proper conventional-commit types (feat, fix, docs, chore, refactor, etc.)
• Keep the subject concise and descriptive
• Specify a relevant scope when it clarifies the change
• List any breaking changes clearly with BREAKING CHANGE
• Keep emoji usage optional and consistent with team policy

Example Use Cases

• Input: Added user authentication with JWT tokens Output: feat(auth): implement JWT-based authentication - Add JWT token generation and validation - Create auth middleware for protected routes - Include refresh token support BREAKING CHANGE: Authentication now required for all /api/* endpoints
• Input: Fix crash on startup when config is missing Output: fix(core): handle missing config gracefully - Validate config presence on startup - Default missing values to safe fallbacks
• Input: Update README to reflect new API endpoints Output: docs(api): update README with new endpoint details - Document new /users and /auth endpoints - Clarify response formats
• Input: Remove deprecated /old-endpoint API Output: refactor(api): remove deprecated /old-endpoint - Remove usage of deprecated route - Update client SDK references
• Input: Improve data fetch performance Output: perf(data-fetch): optimize query caching - Add result caching for frequent queries - Reduce redundant requests

Frequently Asked Questions