skills.rest
tnkmr32
tnkmr32COMMUNITY
Explore all skills by this author →
GitHub

git-commit

Generate Conventional Commit messages from git diffs with optional body and footers.

Updated Dec 16, 2025
Search Tags:#automation#git#commit#cli#diff#conventional-commit
One-click install
npx skills add https://github.com/tnkmr32/expo-app-20251119 --skill git-commit-tnkmr32
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/tnkmr32/expo-app-20251119/tree/main/.github/skills/git-commit
Command: npx skills add https://github.com/tnkmr32/expo-app-20251119 --skill git-commit-tnkmr32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates inconsistent, manually crafted git commit messages by automatically generating Conventional Commit messages from diffs.

Core Features & Use Cases

  • Automatic Conventional Commit generation from code diffs, extracting type, scope, and description.
  • Interactive override: adjust type/scope/description as needed before committing.
  • Support for optional body, footer, and breaking-change notes to capture context.

Quick Start

Run the git-commit workflow to generate a Conventional Commit from your staged changes. Stage changes with git add and then invoke the skill to create the commit 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 a git diff?▼

To generate a conventional commit message, stage your code changes and run the workflow to automatically extract the type, scope, and description from the diff to standardize your git history.

What is the best way to automate standardizing git history across features and fixes?▼

Automating git history standardization involves generating conventional commit messages directly from code diffs, ensuring consistent formatting for features, fixes, docs, and refactors without manual message crafting.

Can I override the generated commit type and scope before committing?▼

Yes, you can use the interactive override feature to adjust the extracted type, scope, and description as needed before finalizing the commit message.

Does this conventional commit generator support adding a body, footer, and breaking change notes?▼

Yes, the conventional commit generator supports optional body, footer, and breaking-change notes to capture additional context alongside the core type, scope, and description extracted from your diff.

Do I need to stage my changes with git add before generating the commit message?▼

Yes, you must stage your changes with git add first; the workflow then analyzes those staged diffs to produce the formatted conventional commit message for your repository.

Related Skills

Explore More Software Engineering Skills→
wesleyosantos91wesleyosantos91
6

commit-message

Generate Conventional Commits messages from git diffs with type and scope.

Community
Basic
victorp1leonvictorp1leon

git-commit

Create conventional git commits from staged changes with validation checks.

Community
Intermediate
dtbuchholzdtbuchholz

commit-push-pr

Stage Git changes, create conventional commits, push branches, and open pull requests via GitHub CLI.

Community
Intermediate
rserse
44

ase-meta-commit

Generate a concise commit message from `git diff --cached` output.

Community
Basic