skills.rest
mgajewskik
mgajewskikCOMMUNITY
Explore all skills by this author →
GitHub

git-commit

Draft git commit messages with Conventional Commit headers and structured bodies.

6|1|Updated Dec 29, 2025
Search Tags:#git#workflow#commit#conventional-commits#scopes#message-generation
One-click install
npx skills add https://github.com/mgajewskik/opencode-config --skill git-commit-mgajewskik
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/mgajewskik/opencode-config/tree/main/skills/git-commit
Command: npx skills add https://github.com/mgajewskik/opencode-config --skill git-commit-mgajewskik

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Drafts precise git commit messages from repository changes, explaining the rationale and impact of each change.

Core Features & Use Cases

  • Turn staged or unstaged changes into Conventional Commit headers.
  • Add a commit body that explains why the change was necessary and what was done.
  • Follow the repository's existing commit taxonomy and flag potential splits when multiple concerns exist.

Quick Start

Draft a commit message for the current changes.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I generate conventional commit messages from staged changes?▼

Generate conventional commit messages by analyzing staged or unstaged repository changes to construct a type header, an optional scope, and an imperative subject line summarizing the updates.

What is the best way to write a git commit body explaining why changes were made?▼

A precise git commit body uses structured Why and What sections to explain the rationale behind the change and detail the specific modifications applied to the codebase.

How does Conventional Commits taxonomy handle multiple unrelated changes in one commit?▼

Conventional Commits taxonomy enforces meaningful split guidance by flagging potential splits when multiple unrelated concerns exist, ensuring commits remain atomic and focused.

Can I add breaking change footers to commit messages using conventional commits?▼

Conventional commits support optional breaking-change footers appended to the message body, clearly signaling backwards-incompatible modifications to automated tooling and developers.

Does this commit message generator work with an existing project commit taxonomy?▼

The commit message generator aligns with the repository's existing commit taxonomy, matching established types and scopes to maintain consistency across the project's history.

Related Skills

Explore More Software Engineering Skills→
forgivesam168forgivesam168
2

git-commit

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

Community
Basic
mattg101mattg101
1

gcp-copy

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

Community
Basic
chiruu12chiruu12
1

ship

Automate software deployment with Git branch management, testing, and pull requests.

Community
Advanced
channingwaltonchanningwalton
3

Commit Helper

Generate conventional commit messages from staged git diffs.

Community
Intermediate