How do I install the Git Commits skill?

Run npx skillmds@latest add tomevault-io/git-commits-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Git Commits safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Commits?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Git Commits free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Git Commits?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Commits by tomevault-io — Agent Skill

Name: Git Commits
Author: tomevault-io

Git Commits

Git commit best practices with conventional commits format and atomic commit principles. Use when committing code to ensure clear, meaningful commit history with proper type prefixes and semantic versioning support. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Git Commits Skill

This skill enforces git commit best practices and conventional commits format.

Conventional Commits Format

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Commit Types

Type	Description	Semver
`feat`	New feature	MINOR
`fix`	Bug fix	PATCH
`docs`	Documentation only	-
`style`	Formatting, no code change	-
`refactor`	Code restructuring	-
`perf`	Performance improvement	PATCH
`test`	Adding tests	-
`chore`	Maintenance tasks	-
`ci`	CI configuration	-
`build`	Build system changes	-

Examples

Feature

feat(auth): add OAuth2 login support

Implement OAuth2 flow with Google and GitHub providers.
Includes token refresh and secure storage.

Closes #123

Bug Fix

fix(api): handle null response in user endpoint

The /users endpoint crashed when the database returned null.
Added proper null checking and error response.

Breaking Change

feat(api)!: change response format for /users endpoint

BREAKING CHANGE: Response now returns array instead of object.
Migration guide available in docs/migrations/v2.md

Atomic Commits

Each commit should:

Represent ONE logical change
Be independently revertible
Pass all tests
Be complete (not "WIP")

Bad Example

git commit -m "Fix bugs and add features and update docs"

Good Example

git commit -m "fix(auth): prevent session timeout on refresh"
git commit -m "feat(dashboard): add export to CSV button"
git commit -m "docs(api): update authentication examples"

Commit Message Rules

Type is required and lowercase
Description starts lowercase, no period
Imperative mood: "add" not "added" or "adds"
First line under 72 characters
Body wraps at 72 characters
Breaking changes marked with ! or footer

Claude Code Commit Footer

When committing with Claude Code, include:

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: git-commits-2description: Git commit best practices with conventional commits format and atomic commit principles. Use when committing code to ensure clear, meaningful commit history with proper type prefixes and semantic versioning support. Use when this capability is needed.---# Git Commits SkillThis skill enforces git commit best practices and conventional commits format.## Conventional Commits Format```<type>[optional scope]: <description>[optional body][optional footer(s)]```## Commit Types| Type | Description | Semver ||------|-------------|--------|| `feat` | New feature | MINOR || `fix` | Bug fix | PATCH || `docs` | Documentation only | - || `style` | Formatting, no code change | - || `refactor` | Code restructuring | - || `perf` | Performance improvement | PATCH || `test` | Adding tests | - || `chore` | Maintenance tasks | - || `ci` | CI configuration | - || `build` | Build system changes | - |## Examples### Feature```feat(auth): add OAuth2 login supportImplement OAuth2 flow with Google and GitHub providers.Includes token refresh and secure storage.Closes #123```### Bug Fix```fix(api): handle null response in user endpointThe /users endpoint crashed when the database returned null.Added proper null checking and error response.```### Breaking Change```feat(api)!: change response format for /users endpointBREAKING CHANGE: Response now returns array instead of object.Migration guide available in docs/migrations/v2.md```## Atomic CommitsEach commit should:1. Represent ONE logical change2. Be independently revertible3. Pass all tests4. Be complete (not "WIP")### Bad Example```git commit -m "Fix bugs and add features and update docs"```### Good Example```git commit -m "fix(auth): prevent session timeout on refresh"git commit -m "feat(dashboard): add export to CSV button"git commit -m "docs(api): update authentication examples"```## Commit Message Rules1. **Type is required** and lowercase2. **Description** starts lowercase, no period3. **Imperative mood**: "add" not "added" or "adds"4. **First line** under 72 characters5. **Body** wraps at 72 characters6. **Breaking changes** marked with `!` or footer## Claude Code Commit FooterWhen committing with Claude Code, include:```🤖 Generated with [Claude Code](https://claude.com/claude-code)Co-Authored-By: Claude <noreply@anthropic.com>```---> Converted and distributed by [TomeVault](https://tomevault.io/claim/jpoutrin) — claim your Tome and manage your conversions.

Frequently asked questions