skills.rest
tho
thoCOMMUNITY
Explore all skills by this author →
GitHub

git-commit

Generate Conventional Commit messages and stage specified paths safely.

1|Updated Jan 29, 2026
Search Tags:#git#diff analysis#conventional commits#breaking changes#staging#commit message
One-click install
npx skills add https://github.com/tho/skills --skill git-commit-tho
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/tho/skills/tree/main/skills/git-commit
Command: npx skills add https://github.com/tho/skills --skill git-commit-tho

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps you turn your changes into a correct, consistent Git commit—choosing the right Conventional Commits type/scope and producing a clear message without you guessing the format.

Core Features & Use Cases

  • Conventional Commit Generation: Selects an appropriate type (and optional scope) based on what changed and writes a <72 character description in the right style.
  • Commit Safety and Scope Control: Detects whether files are already staged, stages only the relevant argument-specified paths/globs, and avoids unsafe broad adds.
  • Guidance for Breaking Changes: Applies breaking change rules using ! and/or BREAKING CHANGE footer semantics and points to the spec for edge cases.
  • Workflow Support for Common Prompts: Works when the user asks to commit, stage and commit, save changes, prepare a commit, write a commit message, or uses /commit.

Quick Start

Ask the AI to prepare a commit for my staged changes using the correct conventional commit type and a properly formatted message.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I generate a conventional commit message from my staged changes?▼

To generate a conventional commit message, the skill analyzes your git diff to infer the type and scope, then produces a clear imperative description under 72 characters for your staged changes.

What is the correct way to indicate breaking changes in a conventional commit?▼

Indicating breaking changes in a conventional commit involves appending a `!` after the type/scope or adding a `BREAKING CHANGE` footer, which this skill applies consistently to your commit messages.

How do I safely stage specific files before creating a git commit?▼

To safely stage specific files before committing, provide the exact file paths or globs so the tool stages only those relevant changes and avoids unsafe broad `git add` patterns.

Can I use this to prepare a commit message without staging all my working tree changes?▼

Yes, you can prepare a commit message without staging everything by specifying exact file paths, allowing the workflow to target only the relevant working tree changes for your commit.

What are the limitations of automatically inferring commit type from a git diff?▼

Inferring commit type from a git diff relies entirely on the file changes detected, meaning complex or ambiguous modifications might require you to manually adjust the generated type or scope.

Related Skills

Explore More Software Engineering Skills→
t-miura-024t-miura-024

mt-check-git-diff

Analyze git repository changes and retrieve detailed diffs for modified files.

Community
Intermediate
JasonLoJasonLo

ss-self-release

Automate version bumping, Git tagging, and pushing to remote repositories.

Community
Advanced
hyperlisthyperlist
271

git-workflow

Enforce Git branching, commit, and pull request standards with automated staging.

Community
Intermediate
nvimcraftnvimcraft

angular-git-commit-style

Generate Angular Conventional Commit messages from staged Git changes.

Community
Intermediate