Skip to content
TakoAPI
Back to skills

conventional-commits

by bastos

Git & GitHub
7.1kDownloads reported by clawskills.sh
4Stars
0Views
0 likesSign in to like this skill
—Not yet rated
Your rating

Brief

Format commit messages using the Conventional.

Description

What This Skill Does

Formats commit messages according to the Conventional Commits specification, which maps commit types like feat and fix to semantic version increments. Structured messages enable automated changelog generation and release tooling.

Structured commit types let release tools like semantic-release determine version bumps automatically without manual tagging or release notes.

When to Use It

  • Writing a commit message for a new feature
  • Marking a breaking API change with the correct notation
  • Scoping a bug fix to a specific module
  • Preparing commits that feed into automated changelog tools
  • Standardizing commit history across a team

Example Workflow

INPUT

User asks: write a commit message for adding OAuth2 login support

AGENT
  1. 1

    Identifies the change as a new feature

  2. 2

    Selects the feat type with an appropriate scope (auth)

  3. 3

    Writes the description in imperative mood, lowercase, no trailing period

  4. 4

    Checks whether any breaking changes require the ! flag or BREAKING CHANGE footer

OUTPUT

feat(auth): add OAuth2 login support

Installation

clawhub install bastos/conventional-commits

Run the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.

Links