kubev2vkubev2v/forklift/.cursor/skills/git-commit/SKILL.md

git-commit

Skill211 starsChanged 27 days agoApache-2.0View on GitHub

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.

We split this skill into the rules it gives an agent

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

0
Common
Most of the 126 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
Run git branch --show-current.
line 14
Distinctive:
Use AskQuestion to ask:
line 18
Distinctive:
Run git diff HEAD and git status to see all changes since the last commit (staged, unstaged, and untracked files).
line 24
Very specific:
If co-author requested, append: Co-authored-by: AI Assistant <noreply@cursor.com>
line 67
Distinctive:
If the user requests a new branch name, follow this convention:
line 71
Distinctive:
Use hyphens to separate words (kebab-case)
line 78
Distinctive:
Keep it short (3–5 words max after the prefix)
line 79
Distinctive:
Use the lowercase Jira ticket as prefix when available
line 80

“Common” is measured: kept by at least 6 in 10 of the 126 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

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 commit type: chore or fix, then ask for scope (deps, docs, ci, test, refactor, lint, build, validation, deployment, etc.)
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

Title Format (PR title validation enforced by CI)

The title (~72 chars max, imperative mood) must match one of these patterns:

With Jira: MTV-XXXX | description
Without Jira (chore): chore(scope): description
Without Jira (fix): fix(scope): description

Important: The chore and fix formats require parentheses with a scope. fix: description is invalid — use fix(scope): description instead. The scope should be a short word describing the area (e.g., deps, docs, ci, deployment, validation).

Full Message Format

With Jira:

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

Without Jira (fix or chore):

fix(scope): <imperative description, ~72 chars total>

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

Resolves: none

Trailers

With Jira: Ref: https://redhat.atlassian.net/browse/MTV-XXXX and Resolves: MTV-XXXX
Without Jira: Resolves: none (required by CI for non-chore commits)
Chore commits: No Resolves: line needed (CI skips validation for chore commits)

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

Step 5: Branch Naming Convention

If the user requests a new branch name, follow this convention:

With Jira: mtv-XXXX-short-description (lowercase ticket, kebab-case summary)
Without Jira: fix-short-description or chore-short-description

Rules:

All lowercase
Use hyphens to separate words (kebab-case)
Keep it short (3–5 words max after the prefix)
Use the lowercase Jira ticket as prefix when available

Examples:

mtv-6189-fix-warm-cutover-naming
fix-protect-system-namespaces
chore-update-dependencies

Step 6: 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
)"

Download now (ZIP)

Other versions164 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 164
github/awesome-copilot★ 41ksame name
doocs/leetcode★ 37ksame name
tisfeng/Easydict★ 15ksame name
doocs/md★ 13ksame name
spinabot/brigade★ 11ksame name
GitTools/GitVersion★ 3.1ksame name
igorescodro/alkaa★ 1.6ksame name
microsoft/hve-core★ 1.6ksame name
mattmireles/gemma-tuner-multimodal★ 1.5ksame name
rohaquinlop/complexipy★ 898same name
154 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use git-pr, github-pr-create and 10 more.
Other files people use alongside this one.
- klauswgSkill
  git-pr
  Prepare, review, publish, or update a complete GitHub pull request for the current repository, including local commit readiness, safe push strategy, semantic title validation, repository-native PR templates, issue linking, and checks verification. Use when the user asks to draft, create, submit, publish, open, or update a pull request. Always require the user to review and explicitly approve the exact final PR before any push or GitHub write.
  Also in 8 projects that use this
- mjun0812Skill
  github-pr-create
  Pull Requestを作成するSkill。現在のbranchからpull requestを作成する。言語指定可能。ユーザーが「PR作って」「pull request作成して」のように依頼したら使うこと。
  Also in 3 projects that use this
- MicrosoftSkill
  git-branch
  Branch management for implementation. Use when you need to create a branch, switch branches, checkout, or verify branching strategy before implementing code. Do not use for commits (use git-commit), pull requests (use pull-request), or advanced git operations (rebase, merge).
  Also in 4 projects that use this
- klauswgSkill
  git-issue
  Prepare, review, create, or update evidence-based GitHub issues for the current repository with duplicate detection, repository-native templates, valid labels, and post-publication verification. Use when the user asks to draft, file, submit, publish, edit, or refine a GitHub issue, bug report, feature request, performance issue, or technical proposal. Always require the user to review and explicitly approve the exact final issue before any GitHub write.
  Also in 3 projects that use this
- MicrosoftSkill
  git-merge
  Integrate branches with merge or rebase, resolve conflicts, and execute an ordinary push when explicitly authorized. Use for guided integration with optional conflict-review pauses.
  Also in 3 projects that use this
- gologo13Skill
  git-push
  Push current branch to origin and sync with remote updates; keywords: git, rebase. Use only on explicit request; before execution, review diffs and list impact scope.
  Also in 4 projects that use this
In this repository2 other files it gives its agents.
- .cursor/rules/minimal-changes.mdcCursor rule
- grill-meSkill

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

Git Commit Skill

Step 1: Check Branch

Step 2: Gather Info

Step 3: Analyze Changes

Step 4: Generate Commit Message

Title Format (PR title validation enforced by CI)

Full Message Format

Trailers

Step 5: Branch Naming Convention

Step 6: Present Message and Command

Word for word · 0

Edited · 0

Wrote their own version · 164

git-pr

github-pr-create

git-branch

git-issue

git-merge

git-push

Does it work?

No reviews yet

Your trail

Now do this for your own.