Format commit messages using the Conventional Commits specification. Use when creating commits, writing commit messages, or when the user mentions commits, git commits, or commit messages. Ensures commits follow the standard format for automated tooling, changelog generation, and semantic versioning.
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
SkillHub CLI
skillhub install bastos/conventional-commitsInspect the source and compatibility requirements, then follow its installation steps.
Give your agent the source link and ask it to inspect instructions and dependencies before explaining the installation steps.
Format all commit messages according to the Conventional Commits specification. This enables automated changelog generation, semantic versioning, and better commit history.
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
feat: - A new feature (correlates with MINOR in Semantic Versioning)fix: - A bug fix (correlates with PATCH in Semantic Versioning)docs: - Documentation only changesstyle: - Code style changes (formatting, missing semicolons, etc.)refactor: - Code refactoring without bug fixes or new featuresperf: - Performance improvementstest: - Adding or updating testsbuild: - Build system or external dependencies changesci: - CI/CD configuration changeschore: - Other changes that don't modify src or test filesrevert: - Reverts a previous commitAn optional scope provides additional contextual information about the section of the codebase:
feat(parser): add ability to parse arrays
fix(auth): resolve token expiration issue
docs(readme): update installation instructions
Breaking changes can be indicated in two ways:
! in the type/scopefeat!: send an email to the customer when a product is shipped
feat(api)!: send an email to the custome...
These signals come from indexed source analysis and may lag behind changes. Check the current source files.
# Conventional Commits
Format all commit messages according to the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification. This enables automated changelog generation, semantic versioning, and better commit history.
## Format Structure
```
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
```
## Commit Types
### Required Types
- **`feat:`** - A new feature (correlates with MINOR in Semantic Versioning)
- **`fix:`** - A bug fix (correlates with PATCH in Semantic Versioning)
### Common Additional Types
- **`docs:`** - Documentation only changes
- **`style:`** - Code style changes (formatting, missing semicolons, etc.)
- **`refactor:`** - Code refactoring without bug fixes or new features
- **`perf:`** - Performance improvements
- **`test:`** - Adding or updating tests
- **`build:`** - Build system or external dependencies changes
- **`ci:`** - CI/CD configuration changes
- **`chore:`** - Other changes that don't modify src or test files
- **`revert:`** - Reverts a previous commit
## Scope
An optional scope provides additional contextual information about the section of the codebase:
```
feat(parser): add ability to parse arrays
fix(auth): resolve token expiration issue
docs(readme): update installation instructions
```
## Description
- Must immediately follow the colon and space after the type/scope
- Use imperative mood ("add feature" not "added feature" or "adds feature")
- Don't capitalize the first letter
- No period at the end
- Keep it concise (typically 50-72 characters)
## Body
- Optional longer description providing additional context
- Must begin one blank line after the description
- Can consist of multiple paragraphs
- Explain the "what" and "why" of the change, not the "how"
## Breaking Changes
Breaking changes can be indicated in two ways:
### 1. Using `!` in the type/scope
```
feat!: send an email to the customer when a product is shipped
feat(api)!: send an email to the custome...Bambu Lab 3D printer control and automation. Activate when user mentions: printer status, 3D printing, slice, analyze model, generate 3D, AMS filament, print monitor, Bambu Lab, or any 3D printing task. Full pi...
University for AI agents. 92 courses, 4400+ scenarios, any model via OpenRouter. Auto-training loops generate per-model SKILL.md documents. Works with Claude Code, OpenClaw, Cursor, Windsurf. No fine-tuning req...
OpenClaw Skill for stock data analysis
Generative Engine Optimization (GEO) for AI search visibility. Optimize content to appear in ChatGPT, Perplexity, Claude, and Google AI Overviews. Use when optimizing websites, pages, or content for LLM discove...