skills.rest
Binh230199
Binh230199COMMUNITY
Explore all skills by this author →
GitHub

git-commit-message

Generate git commit messages from staged, unstaged, or historical changes.

1|Updated Feb 28, 2026
Search Tags:#git#jira#version-control#commit-message#conventional-commits#diff-analysis
One-click install
npx skills add https://github.com/Binh230199/ai --skill git-commit-message-binh230199
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit-message
Source: https://github.com/Binh230199/ai/tree/main/.github/skills/git-commit-message
Command: npx skills add https://github.com/Binh230199/ai --skill git-commit-message-binh230199

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the guesswork from writing git commit messages by turning diffs and repository history into a message that matches the project's existing style.

Core Features & Use Cases

  • Infers commit type and scope from the files that changed.
  • Adapts to a repository-specific template or falls back to recent commit history when no template exists.
  • Handles staged changes, unstaged changes, and past commits, while checking subject length, body structure, and ticket references.
  • Use case: after finishing a code change, generate a copy-ready commit message without memorizing the team's format.

Quick Start

Ask the skill to generate a commit message for the current staged changes.

Frequently Asked Questions about git-commit-message

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a git commit message from staged changes that matches my repo style?▼

Generate a git commit message from staged changes by applying the repository's existing template or recent commit history. The output matches inferred commit type, scope, subject length, and body formatting automatically.

Can I write conventional commits automatically from a git diff?▼

Write conventional commits from a git diff by inferring the commit type and scope from changed files. The generated message enforces subject-length limits, tense rules, and body structure required by conventional commits.

Does this commit message generator work with unstaged changes or historical commits?▼

The commit message generator works with staged changes, unstaged changes, and past commits. It analyzes code, documentation, and mixed repository diffs to produce a ready-to-use message.

How do I include a Jira ticket reference in a conventional commit message?▼

Include a Jira ticket reference in a conventional commit message by applying footer formatting rules. The generated output adds required ticket references to the commit footer when specified.

What's the best way to format commit messages for a project with no commit template?▼

Format commit messages for projects with no template by falling back to recent commit history. The generator analyzes past commits to infer subject tense, length limits, and body structure for style matching.

Why do my generated commit messages fail to match my team's version-control conventions?▼

Generated commit messages fail to match version-control conventions when the template or history lacks consistent type, scope, and subject-length rules. The generator applies existing repo patterns to ensure style alignment.

Related Skills

Explore More Software Engineering Skills→
githubgithub
37.6k

git-commit

Analyze git diffs to generate conventional commit messages and stage files.

Official
Intermediate
mattg101mattg101
1

gcp-copy

Stage all changes, commit with a message, and push to a remote Git repository.

Community
Basic
aldy505aldy505

commit

Generate Git commit messages following Sentry conventional commit standards.

Community
Intermediate
shysssthanhtrishysssthanhtri

conventional-commit

Generate Conventional Commit messages from staged Git diffs with Jira ticket IDs.

Community
Intermediate