Commit Message

Community

danielvm-git

commit-message

Reviews working-tree changes, then drafts a Conventional Commits title/body and states the semantic-release version bump a single such commit would imply. Also notes which defensive-code categories were touched. Use when the user wants to commit recent work, prepare a Conventional Commits message, or asks for semantic-release / semver-consistent messaging before git commit.

Overview

Publisher	danielvm-git
Repository	`bigpowers`
Skill name	`commit-message`
Stars	206
Forks	18
Bundled files	1
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.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by danielvm-git on GitHub. Read the source before you install it.

Installation

Install the Commit Message 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.
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/danielvm-git/bigpowers.git /tmp/bigpowers
mkdir -p .claude/skills
cp -r /tmp/bigpowers/skills/commit-message .claude/skills/commit-message

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

Use it in TypingMind

Enable Commit Message 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 Message 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 Message 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.

story: e82s02

Commit Message

HARD GATE — HARD GATE — Commits must follow Conventional Commits spec (type(scope): description). Do NOT use vague messages like 'fix' or 'updates.' The message must explain the 'why,' not the 'what.'

Modes

Default: standard Conventional Commits message
--fix-type: Forces type=fix. Use when commit type is unambiguous.

What "last chat" means

Primary source of truth: Read state.yaml vcs.kind. Git uses git status, git diff, and git diff --cached; Jujutsu uses jj status, jj diff, and jj log -r @. Run in the repo root.
Context: use the current conversation to summarize intent and to spot breaking API/behavior changes that diff alone may not show.
If the user tracks a session baseline (e.g. branch, tag, or git stash create at start), you may git diff <baseline>..HEAD plus uncommitted diffs; otherwise use only the index and working tree.

Quick workflow

Inventory — List changed paths; group by feature vs chore vs docs vs test-only.
Decide commit shape — One atomic commit is ideal. If the diff mixes unrelated concerns, recommend multiple commits (each with its own type/scope) before suggesting one message.
Classify for semantic release — fix → patch, feat → minor, breaking → major.
Write the message — type(optional-scope)!: description (see REFERENCE.md). Use ! or a BREAKING CHANGE: footer when behavior contracts change.
Note defensive-code categories touched — from CONVENTIONS.md: Rate limit | Retry with backoff | Circuit breaker | Timeout | Graceful degradation
Note fix-ratio contribution — Each fix: commit counts toward metrics.commit_ratio.fix in specs/state.yaml. After release-branch, session-state recalculates the ratio automatically. A high fix rate (>30%) triggers a deploy + smoke-test suggestion.
Deliver — Output:
- Proposed full commit message (title + optional body + footers).
- Release bump this commit would drive: patch | minor | major | none.
- Optional native command: Git git commit -m; Jujutsu jj commit -m. Never omit -m or run destructive commands unless asked.

Checklist before finalizing

Type matches the dominant user-visible outcome (feat vs fix vs perf, etc.).
Scope is a short noun in parentheses if it helps (e.g. fix(api): …).
Breaking changes are explicit (! and/or BREAKING CHANGE: in the body/footer).
Description is imperative, lowercase start after the prefix, no trailing period in the title line.
NO Co-authored-by or Co-Authored-By footers — P1 rule (CONVENTIONS.md § Git Attribution). All commits must appear as if authored solely by the human user. The git hook and land-branch.sh both block these.

When not to invent a bump

If the repo uses a custom @semantic-release/commit-analyzer preset, note that your bump is heuristic and they should match .releaserc / release.config.*. See REFERENCE.md.

Handoff

Gate: READY -> next: release-branch Writes: state.yaml handoff.next_skill = release-branch

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

REFERENCE.md4 KB

Frequently asked questions

What does the Commit Message AI skill do?

Why use Commit Message on TypingMind?

Because you install it once and use it with any model. Commit Message 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 Message in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/danielvm-git/bigpowers/tree/main/skills/commit-message. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Commit Message?

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 Message?

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

Is the Commit Message AI skill free?

Yes. It is published on GitHub by danielvm-git 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

Test Driven Development

obra

CommunityPopular

Use when implementing any feature or bugfix, before writing implementation code

Using Git Worktrees

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback

Using Superpowers

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

Verification Before Completion

obra

CommunityPopular

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence…

Commit Message

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

story: e82s02

Commit Message

Modes

What "last chat" means

Quick workflow

Checklist before finalizing

When not to invent a bump

Further reading

Handoff

Bundled files

Frequently asked questions

Set up your own AI workspace now

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

story: e82s02

Commit Message

Modes

What "last chat" means

Quick workflow

Checklist before finalizing

When not to invent a bump

Further reading

Handoff

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now