ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified developer tools Safety 5/5

conventional-commits

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.

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/bastos/conventional-commits
Or

What This Skill Does

The conventional-commits skill provides the OpenClaw AI agent with the capability to format git commit messages strictly according to the Conventional Commits specification. This industry-standard protocol transforms commit history into a structured, machine-readable format. By enforcing types such as 'feat', 'fix', 'refactor', and 'chore', the skill enables downstream automation tools to generate professional changelogs, perform semantic versioning (SemVer) automatically, and provide clearer insights into the evolution of a codebase. It handles complex requirements, including scopes, imperative mood descriptions, extended bodies, and explicit breaking change footers (marked with '!' or 'BREAKING CHANGE:').

Installation

To integrate this functionality into your OpenClaw environment, execute the following command in your terminal:

clawhub install openclaw/skills/skills/bastos/conventional-commits

Once installed, the agent will automatically recognize requests related to git operations and suggest or rewrite commit messages to adhere to the specification.

Use Cases

  • Automating changelog generation for CI/CD pipelines.
  • Ensuring consistent team communication in large-scale software projects.
  • Supporting automated release workflows where semantic versioning is determined by commit types (e.g., 'feat' triggers a minor update, 'fix' triggers a patch).
  • Standardizing commit history for easier auditing and navigation by other developers.

Example Prompts

  1. "I just updated the user authentication logic to include JWT tokens, write me a commit message for this."
  2. "Please rewrite this commit message to be a proper conventional commit: 'Fixing the bug where the profile page crashes on load'."
  3. "I am removing support for the legacy API v1, how should I format this as a breaking change commit?"

Tips & Limitations

  • Be Concise: Always use the imperative mood (e.g., 'add' instead of 'added') and keep the header line under 72 characters.
  • Use Scopes: When working in large repositories, use scopes (e.g., feat(ui): ...) to make the history searchable and filtered by module.
  • Breaking Changes: When introducing a breaking change, use the '!' suffix or the 'BREAKING CHANGE' footer; failing to do so will prevent automated release tools from correctly identifying the version increment.
  • Limitations: This skill does not interact with your Git provider directly. It provides text generation and formatting advice. You must still execute the actual git commit command in your terminal or via a separate git-interaction skill.
Read Full Documentation on GitHub

Metadata

Author@bastos
Stars4473
Views0
Updated2026-05-01
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-bastos-conventional-commits": {
      "enabled": true,
      "auto_update": true
    }
  }
}

Tags(AI)

#git#commits#developer-tools#automation#versioning
Safety Score: 5/5

Related Skills

topydo

Manage todo.txt tasks using topydo CLI. Add, list, complete, prioritize, tag, and organize tasks with dependencies, due dates, recurrence, and projects. Use for any task management, todo lists, or when the user mentions tasks, todos, or todo.txt. Requires Python 3 and pip. Works on macOS, Linux, and Windows.

bastos 4473

Obsidian Daily

Skill by bastos

bastos 4473

pass

Complete guide for using pass, the standard Unix password manager. Use this skill whenever the user asks about pass, password-store, managing passwords from the terminal, GPG-encrypted passwords, setting up pass for the first time, inserting or generating passwords, syncing a password store with git, using pass-otp for TOTP codes, importing passwords from another manager, or any task involving the `pass` CLI. Trigger on phrases like "set up pass", "add a password to pass", "sync my password store", "generate a password", "pass git", "pass-otp", "pass-import", or any variation.

bastos 4473