How do I install the Git Commit skill?

Run npx skillmds@latest add tomevault-io/git-commit-5 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 Commit 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 Commit?

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 Commit free to use?

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

Who published Git Commit?

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

Git Commit by tomevault-io — Agent Skill

Name: Git Commit
Author: tomevault-io

Git Commit

Compose CI-valid commit messages with Jira linking and sign-off. Use when the user asks to commit, write a commit message, or git commit. Never execute the commit — only present the message and command for the user to run. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Git Commit Skill

Never run git add or git commit yourself. The user will review, adjust if needed, and execute the commit manually.

For full commit message validation rules, formats, and troubleshooting, see commit-message-guide.md in this skill directory.

Step 1: Check Branch

Run git branch --show-current. If on main, warn the user and ask if they want to continue or switch to a new branch first.

Step 2: Gather Info

Use AskQuestion to ask:

Jira issue ID (e.g. MTV-1234) — if "None", ask for chore type (deps, docs, ci, test, refactor, lint, build)
Add AI co-author line? (Yes / No)

Step 3: Analyze Changes

Run git diff HEAD and git status to see all changes since the last commit (staged, unstaged, and untracked files). Use these diffs to understand what changed and why.

Step 4: Generate Commit Message

Format:

MTV-XXXX | <imperative description, ~72 chars total>

<body: what changed and why, lines wrapped at 72 chars>

Ref: https://redhat.atlassian.net/browse/MTV-XXXX
Resolves: MTV-XXXX

Title (~72 chars max, imperative mood):

With Jira: MTV-XXXX | description
Without Jira: chore(type): description (skips CI — no Ref:/Resolves: needed)

Trailers (with Jira only):

Ref: https://redhat.atlassian.net/browse/MTV-XXXX
Resolves: MTV-XXXX (required by CI)

If co-author requested, append: Co-authored-by: AI Assistant <noreply@cursor.com>

Step 5: Present Message and Command

Present the full commit message in a code block, followed by a ready-to-run git command the user can copy-paste:

git add <relevant files>
git commit -s -m "$(cat <<'EOF'
<the commit message>
EOF
)"

Source: kubev2v/forklift — distributed by TomeVault.

---name: git-commit-5description: Compose CI-valid commit messages with Jira linking and sign-off. Use when the user asks to commit, write a commit message, or git commit. Never execute the commit — only present the message and command for the user to run. Use when this capability is needed.---# Git Commit Skill**Never run `git add` or `git commit` yourself.** The user will review, adjust if needed, and execute the commit manually.For full commit message validation rules, formats, and troubleshooting, see [commit-message-guide.md](commit-message-guide.md) in this skill directory.## Step 1: Check BranchRun `git branch --show-current`. If on `main`, **warn the user** and ask if they want to continue or switch to a new branch first.## Step 2: Gather InfoUse AskQuestion to ask:1. **Jira issue ID** (e.g. `MTV-1234`) — if "None", ask for **chore type** (deps, docs, ci, test, refactor, lint, build)2. **Add AI co-author line?** (Yes / No)## Step 3: Analyze ChangesRun `git diff HEAD` and `git status` to see all changes since the last commit (staged, unstaged, and untracked files). Use these diffs to understand what changed and why.## Step 4: Generate Commit MessageFormat:```MTV-XXXX | <imperative description, ~72 chars total><body: what changed and why, lines wrapped at 72 chars>Ref: https://redhat.atlassian.net/browse/MTV-XXXXResolves: MTV-XXXX```Title (~72 chars max, imperative mood):- **With Jira:** `MTV-XXXX | description`- **Without Jira:** `chore(type): description` (skips CI — no `Ref:`/`Resolves:` needed)Trailers (with Jira only):- `Ref: https://redhat.atlassian.net/browse/MTV-XXXX`- `Resolves: MTV-XXXX` (required by CI)If co-author requested, append: `Co-authored-by: AI Assistant <noreply@cursor.com>`## Step 5: Present Message and CommandPresent the full commit message in a code block, followed by a ready-to-run `git` command the user can copy-paste:```bashgit add <relevant files>git commit -s -m "$(cat <<'EOF'<the commit message>EOF)"```---> Source: [kubev2v/forklift](https://github.com/kubev2v/forklift) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions