Conventional Commit Message Generator
Generate conventional commit messages following the Conventional Commits specification, without scope prefix.
When to Use
- You have staged changes and need a properly formatted commit message
- You want commit messages that follow conventional commits format
- You need concise messages without scope (e.g.,
fix: descriptioninstead offix(scope): description)
Procedure
- Stage your changes using git add
- Invoke this skill in chat
- The skill will:
- Fetch staged changes using
#git_diff_staged - Analyze the changes to determine commit type (fix, feat, refactor, etc.)
- Extract the primary file name from changes
- Generate a conventional commit message in format:
type: description in \FileName``
- Fetch staged changes using
Commit Message Format
type: description in `FileName`
Supported Types
fix- Bug fixesfeat- New featuresrefactor- Code refactoringdocs- Documentation changesstyle- Code style changes (formatting, etc.)test- Test additions or updateschore- Build, dependencies, tooling
Examples
fix: improve form initialization and modal state handling based on fetch completion in `QualityCheckResultsModal`
feat: add authentication guard to protected routes in `AuthGuard`
refactor: simplify data validation logic in `FormValidator`