Commit Message

Generate conventional commit messages with automatic scope detection.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/tiagofur/kakoclaw --skill commit-message-tiagofur
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Commit Message
Source: https://github.com/tiagofur/kakoclaw/tree/main/.context/skills/commit-message
Command: npx skills add https://github.com/tiagofur/kakoclaw --skill commit-message-tiagofur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of inconsistent and hard-to-read commit messages by automatically generating messages that follow the Conventional Commits format and detect the scope of changes.

Core Features & Use Cases

  • Automatic Conventional Commits: Generate messages that conform to the Conventional Commits specification.
  • Scope Detection: Infers the affected area from the code changes or user input.
  • Use Case: When you finish a feature or fix, run this to produce a precise, scannable commit message that includes the scope.

Quick Start

Provide a concise conventional commit message with an appropriate scope for your latest changes.

Frequently Asked Questions about Commit Message

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate conventional commit messages automatically?

You generate conventional commit messages by providing your code changes or a description of your updates, and the Skill infers the affected scope to output a properly formatted, scannable message.

What is scope detection in conventional commits?

Scope detection in conventional commits identifies the affected codebase area by analyzing code changes or user input, ensuring your commit history remains precise and scannable across features and refactors.

How do I write a git commit message for a specific feature or fix?

To write a git commit message for a feature or fix, apply Conventional Commits rules to your changes, automatically determining the appropriate scope and formatting a consistent, scannable message.

Do I need any specific developer tools to automate commit message generation?

No specific developer tools or dependencies are required to automate commit message generation. You only need to provide your code changes or a concise description of your latest updates to produce a conventional commit.

What is the best way to maintain a consistent git history for refactors?

The best way to maintain a consistent git history for refactors is to use Conventional Commits formatting with scope detection, producing precise, scannable messages that accurately reflect the affected codebase areas.