Commit

OrganizationPopular

ccusage

commit

Creates atomic Conventional Commits. Use when committing code changes, splitting a diff into independently revertable hunks, staging precise patches non-interactively, or writing commit messages.

Overview

Publisher	ccusage
Repository	`ccusage`
Skill name	`commit`
Stars	19K
Forks	871
Bundled files	2
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.
2 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by ccusage on GitHub. Read the source before you install it.

Installation

Install the Commit 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/ccusage/ccusage/tree/main/.agents/skills/commit
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/ccusage/ccusage.git /tmp/ccusage
mkdir -p .claude/skills
cp -r /tmp/ccusage/.agents/skills/commit .claude/skills/commit

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

Use it in TypingMind

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

Arguments:

push: push after committing (default: false).

Workflow

Read the state and recent history — git status --short, git diff HEAD, git log --oneline -10 — and match the granularity, scopes, and explanation style already in the log.
Split the diff into independently revertable units, hunk by hunk rather than file by file.
Stage each unit with git apply --cached -v <patch>. git add -p and git add --interactive hang in this environment, so a patch is the only way to stage part of a file. Read references/git-apply.md when one fails to apply.
Commit, then confirm with git show HEAD.

Revertability

Every commit answers "if I revert this alone, does anything else break?". Tiny commits are expected: one review comment, one wording correction, one reference-file extraction.

Tiny is not partial. A move, rename, or extraction lands as a single commit holding both sides — old path removed, new path added, references updated, generated links synced.

Keep separate concerns in separate commits even when each change is correct, so reverting one concern does not revert unrelated work.

PR branches are squash-merged, so review fixes stack as follow-up commits. Amend only unpublished local mistakes, or when the user asks.

Messages

The subject names the artifact or behavior changed and reads sensibly alone in a commit list; reviewer context goes in the body. Prefer docs(skills): clarify reference routing with a body citing the CodeRabbit feedback over chore: address review feedback. The body wraps at 72 columns and covers problem, rationale, decisions, and impact.

The commit-msg hook runs scripts/validate-commit-scope.nu: when staged paths live under rust/adapters/<agent>/, the scope must be that agent (fix(kimi)), one of the cross-cutting scopes, or — for a change spanning several agents — a workspace scope. rust/adapters/common/ derives adapter, not common. Read the script for the current lists; no other part of the tree derives a scope.

Formatter-only changes are chore: format, or chore(<scope>): format when the scope rule above applies. Messages are US English.

Push (push=true)

Changes reach main through a PR, so commit on a feature branch; references/push.md has the branch and upstream checks.

Push once every commit is in place and let the hooks in nix/git-hooks.nix run — treefmt and gitleaks on commit; treefmt, gitleaks, oxlint, clippy -D warnings, node test, and cargo test on push. Their failures are part of normal validation, so fix them in a new small commit.

Bundled files

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

references/git-apply.md1 KB
references/push.md1 KB

Frequently asked questions

What does the Commit AI skill do?

Creates atomic Conventional Commits. Use when committing code changes, splitting a diff into independently revertable hunks, staging precise patches non-interactively, or writing commit messages.

Why use Commit on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ccusage/ccusage/tree/main/.agents/skills/commit. 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?

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?

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

Is the Commit AI skill free?

It is published on GitHub by ccusage. Check the repository for licensing terms. 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 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.

Release Openclaw Mac

Run or recover OpenClaw macOS release signing, notarization, appcast, and asset promotion.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Commit

Workflow

Revertability

Messages

Push (push=true)

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now