skills.rest
Thiago-Cruz-eng
Thiago-Cruz-engCOMMUNITY
Explore all skills by this author →
GitHub

git-commit

Generates standardized Conventional Commits by analyzing staged or working-tree diffs.

Updated Dec 20, 2023
Search Tags:#git#diff analysis#version control#conventional-commits#developer tooling#commit message generation#intelligent staging
One-click install
npx skills add https://github.com/Thiago-Cruz-eng/Hibrygame --skill git-commit-thiago-cruz-eng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/Thiago-Cruz-eng/Hibrygame/tree/main/.claude/skills/git-commit
Command: npx skills add https://github.com/Thiago-Cruz-eng/Hibrygame --skill git-commit-thiago-cruz-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of writing inconsistent, unclear commit messages by helping you generate and standardize Conventional Commits based on what actually changed in your repository.

Core Features & Use Cases

  • Auto-detect type and scope from changes so the commit message matches the real diff instead of relying on memory.
  • Generate Conventional Commit messages from the diff to produce a one-line summary (and optionally a body/footer) in the correct format.
  • Interactive commit with overrides for cases where the detected intent needs a manual correction.
  • Intelligent staging and logical grouping to ensure the commit includes the right files before committing.

Quick Start

Use git-commit to create a Conventional Commit from your current changes (or staged changes) for example when you are about to commit a bug fix and want a message like fix[scope]: <description>.

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 a git diff?▼

To generate conventional commit messages from a git diff, this Skill analyzes your staged or working-tree changes to automatically determine the appropriate type, scope, and description for your commit.

What is the best way to group staged files into a logical git commit?▼

The best way to group staged files into a logical git commit is using intelligent staging, which analyzes your working-tree diff to ensure the commit includes the right files based on the actual repository changes.

Can I override the auto-detected type and scope for a conventional commit?▼

Yes, you can override the auto-detected type and scope for a conventional commit, providing interactive manual corrections when the detected intent from the diff analysis needs adjustments.

Does this tool execute git commit non-destructively when generating messages?▼

Yes, this tool executes git commit using non-destructive defaults, safely creating your standardized conventional commit messages only after analyzing the staged diff and applying any interactive overrides.

Why should I use conventional commits for my version control workflow?▼

You should use conventional commits for your version control workflow to solve the problem of writing inconsistent, unclear messages by standardizing commit types and scopes based on actual repository changes.

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
AstrumonAstrumon

changelog-generator

Generate Keep a Changelog entries from Conventional Commits history.

Community
Intermediate
sangrokjungsangrokjung
1

fix

Automates lint error fixes and formatting enforcement via yarn linc and prettier scripts.

Community
Basic
sabertazimisabertazimi

generating-commits

Generate Conventional Commits messages and commit staged changes.

Community
Advanced