A guide for writing Git commit messages in Conventional Commits format, a shared pattern that labels changes such as features, fixes, tests, and documentation.

Creating commit subjects, optional explanations, issue references, and breaking-change notes.

It makes commit history consistent and easier to scan, search, and use in automated release tools.

git-commit — Skill by ThinkInAIXYZ

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/thinkinaixyz/deepchat/git-commit

Any agent

npx skills add ThinkInAIXYZ/deepchat --skill git-commit

Clone the repo

git clone --depth 1 https://github.com/ThinkInAIXYZ/deepchat

Made for: Claude Code, Codex.

Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 391 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00015	$0.00391
Opus 5	$0.00008	$0.00196
Sonnet 5	$0.00003	$0.00078
Haiku 4.5	$0.00002	$0.00039

Measured 2d ago against content hash 5beee50560cb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

git-commit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

resources/skills/git-commit/SKILL.md · 60 lines

What it actually says

Git Commit Message Skill

You are a git commit message expert. When this skill is activated, help users create well-structured commit messages.

Commit Message Format

Follow the Conventional Commits specification:

<type>(<scope>): <subject>

[optional body]

[optional footer(s)]

Types

feat: A new feature
fix: A bug fix
docs: Documentation only changes
style: Changes that do not affect the meaning of the code
refactor: A code change that neither fixes a bug nor adds a feature
perf: A code change that improves performance
test: Adding missing tests or correcting existing tests
build: Changes that affect the build system or external dependencies
ci: Changes to CI configuration files and scripts
chore: Other changes that don't modify src or test files

Guidelines

Subject Line
- Use imperative mood ("add" not "added")
- Don't capitalize first letter
- No period at the end
- Limit to 50 characters
Body
- Explain what and why, not how
- Wrap at 72 characters
- Separate from subject with a blank line
Footer
- Reference issues: Fixes #123
- Breaking changes: BREAKING CHANGE: description

Workflow

Run git diff --staged or git status to see changes
Analyze the changes to understand what was modified
Generate an appropriate commit message
Optionally run git commit -m "message" if user confirms

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 60 lines · 15 tokens per session scan A 5beee50560cb

Subscribe to this mod's changes

git-commit is a skill published in the GitHub repository ThinkInAIXYZ/deepchat (6,293 stars, last pushed 4d ago), licensed Apache-2.0. It adds 15 tokens to every session and 391 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Data and AI Git and workflow Testing ai ai-assistant chatgpt cross-platform llm-client openai-client

gitnexus-guide

Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?".

TabularisDB/tabularis · 56 tokens

tabularis-plugin-driver

Use when creating or updating a Tabularis database driver plugin in Rust. Covers modern manifest fields, JSON-RPC over stdio, modular plugin layout, MySQL-level feature coverage targets, optional UI extensions, and validation against Tabularis repo rules.

TabularisDB/tabularis · 57 tokens

tabularis-pr-review

Use when reviewing a Tabularis pull request locally — checking code quality against the repo's own rules, verifying the PR's claims, running its tests on the correct branch, and preparing real test data plus a manual test plan for the human. Use when the user says 'review PR #N', 'lass uns PR reviewen', 'check this…

TabularisDB/tabularis · 90 tokens

git-commit