Git Commit

OrganizationPopular

spinabot

git-commit

Stage, write, and structure git commits and pull requests cleanly. Read this before committing — for conventional-commit message format, when to split commits, and how to open a PR with the gh CLI.

Overview

Publisher	spinabot
Repository	`brigade`
Skill name	`git-commit`
Stars	4.4K
Forks	50
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 spinabot on GitHub. Read the source before you install it.

Installation

Install the Git 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.
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/spinabot/brigade.git /tmp/brigade
mkdir -p .claude/skills
cp -r /tmp/brigade/skills/git-commit .claude/skills/git-commit

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

Use it in TypingMind

Enable Git 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 Git 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 Git 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.

Git commits & PRs

Use this when committing changes or opening a pull request.

Before committing

Run git status and git diff --staged to see exactly what's going in. Never git add -A blindly — stage the files that belong to this change.
Keep one logical change per commit. If the diff does two unrelated things, make two commits.
Don't commit secrets, large binaries, or generated artifacts. Check .gitignore covers them.

Message format

Conventional Commits:


<type>(<optional scope>): <short imperative summary>

<optional body — what changed and WHY, wrapped at ~72 cols>

Types: feat, fix, docs, refactor, test, chore, perf, build, ci.

Summary in the imperative mood ("add", not "added"), ≤72 chars, no trailing period.
The body explains the reasoning a future reader needs — not a restatement of the diff.

Pull requests (gh CLI)

git push -u origin <branch> then gh pr create --fill (or --title/--body).
PR body: what changed, why, and how it was verified (tests run, manual checks).
Confirm the base branch is correct before creating.

Conventions to honor

Match the repository's existing style — read recent git log --oneline first and follow whatever format the project already uses if it differs from the above.

Frequently asked questions

What does the Git Commit AI skill do?

Stage, write, and structure git commits and pull requests cleanly. Read this before committing — for conventional-commit message format, when to split commits, and how to open a PR with the gh CLI.

Why use Git Commit on TypingMind?

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

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

Which AI models can use Git 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 Git Commit?

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

Is the Git Commit AI skill free?

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

Writing Plans

obra

CommunityPopular

Use when you have a spec or requirements for a multi-step task, before touching code

Ask Matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

Code Review

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what…

Codebase Design

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Git commits & PRs

Before committing

Message format

Pull requests (gh CLI)

Conventions to honor

Frequently asked questions

Related AI Skills

Set up your own AI workspace now