Commit Messages

Community

TheDecipherist

commit-messages

Generate clear, conventional commit messages from git diffs. Use when writing commit messages, reviewing staged changes, or preparing releases.

Overview

Publisher	TheDecipherist
Repository	`claude-code-mastery`
Skill name	`commit-messages`
Stars	551
Forks	48
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by TheDecipherist on GitHub. Read the source before you install it.

Installation

Install the Commit Messages AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/TheDecipherist/claude-code-mastery/tree/main/skills/commit-messages
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/TheDecipherist/claude-code-mastery.git /tmp/claude-code-mastery
mkdir -p .claude/skills
cp -r /tmp/claude-code-mastery/skills/commit-messages .claude/skills/commit-messages

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Commit Messages in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Commit Messages on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Commit Messages is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Commit Message Skill

Generate consistent, informative commit messages following the Conventional Commits specification.

When to Use This Skill

User asks to "commit", "write a commit message", or "prepare commit"
User has staged changes and mentions commits
Before any git commit command

Process

Analyze changes: Run git diff --staged to see what's being committed
Identify the type: Determine the primary change category
Find the scope: Identify the main area affected
Write the message: Follow the format below

Commit Message Format


<type>(<scope>): <description>

[optional body]

[optional footer(s)]

Types

Type	Description	Example
`feat`	New feature	`feat(auth): add OAuth2 login`
`fix`	Bug fix	`fix(api): handle null response`
`docs`	Documentation only	`docs(readme): add setup instructions`
`style`	Formatting, no code change	`style: fix indentation`
`refactor`	Code change, no new feature/fix	`refactor(db): extract query builder`
`perf`	Performance improvement	`perf(search): add result caching`
`test`	Adding/fixing tests	`test(auth): add login unit tests`
`build`	Build system changes	`build: update webpack config`
`ci`	CI configuration	`ci: add GitHub Actions workflow`
`chore`	Maintenance tasks	`chore(deps): update dependencies`
`revert`	Revert previous commit	`revert: feat(auth): add OAuth2`

Scope

The scope should be a noun describing the section of the codebase:

auth, api, db, ui, config
Feature names: search, checkout, dashboard
Or omit if change is broad

Subject Line Rules

Use imperative mood: "add" not "added" or "adds"
Don't capitalize first letter after colon
No period at the end
Max 72 characters total

Body (when needed)

Separate from subject with blank line
Explain what and why, not how
Wrap at 72 characters
Use bullet points for multiple changes

Footer (when needed)

BREAKING CHANGE: for breaking changes
Fixes #123 to close issues
Refs #456 to reference without closing

Examples

Simple feature


feat(search): add fuzzy matching support

Implement Levenshtein distance algorithm for typo tolerance
in search queries. Configurable via FUZZY_THRESHOLD env var.

Bug fix with issue reference


fix(cart): prevent duplicate items on rapid clicks

Add debounce to add-to-cart button and check for existing
items before insertion.

Fixes #234

Breaking change


feat(api)!: change response format to JSON:API

BREAKING CHANGE: API responses now follow JSON:API spec.
All clients need to update their parsers.

- Wrap data in `data` object
- Move metadata to `meta` object  
- Add `links` for pagination

Multiple related changes


refactor(auth): consolidate authentication logic

- Extract JWT handling to dedicated service
- Move session management from controller to middleware
- Add refresh token rotation

This prepares for the upcoming OAuth2 integration.

Output

When generating a commit message:

Show the staged changes summary
Propose the commit message
Explain the type/scope choice if non-obvious
Ask if the user wants to proceed or modify

Frequently asked questions

What does the Commit Messages AI skill do?

Generate clear, conventional commit messages from git diffs. Use when writing commit messages, reviewing staged changes, or preparing releases.

Why use Commit Messages on TypingMind?

Because you install it once and use it with any model. Commit Messages is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Commit Messages in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/TheDecipherist/claude-code-mastery/tree/main/skills/commit-messages. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Commit Messages?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Commit Messages?

As many as you like. As long as a model supports skills, you can use Commit Messages with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Commit Messages AI skill free?

Yes. It is published on GitHub by TheDecipherist under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Openclaw Repair Sweep

openclaw

OrganizationPopular

Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.

Openclaw Test Performance

openclaw

OrganizationPopular

Benchmark, diagnose, and optimize OpenClaw test and plugin-suite runtime, import hotspots, CPU/RSS, heap growth, and slow coverage paths.

Openclaw Testing

Choose proportional OpenClaw tests and checks, diagnose failures, and route environment-sensitive or release proof to its owner.

Release Openclaw Ci

Run, watch, debug, and summarize OpenClaw full release CI, release checks, live provider gates, install/update proofs, and release-secret preflights.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Commit Message Skill

When to Use This Skill

Process

Commit Message Format

Types

Scope

Subject Line Rules

Body (when needed)

Footer (when needed)

Examples

Simple feature

Bug fix with issue reference

Breaking change

Multiple related changes

Output

Frequently asked questions

Related AI Skills

Set up your own AI workspace now