git-commit

Generate Conventional Commits messages from repository diffs and stage files.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/BrunoAMSilva/my-config --skill git-commit-brunoamsilva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/BrunoAMSilva/my-config/tree/main/coding/skills/git-commit
Command: npx skills add https://github.com/BrunoAMSilva/my-config --skill git-commit-brunoamsilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many developers struggle to write consistent, informative commit messages and to stage related changes logically, resulting in noisy history and poor traceability; this Skill standardizes commit messages using the Conventional Commits format and assists with intelligent staging so commits are clear and atomic.

Core Features & Use Cases

  • Intelligent diff analysis to infer commit type (feat, fix, docs, etc.) and likely scope based on changed files.
  • Generate concise, Conventional Commits–compliant messages with optional body and footers, and support interactive overrides for type, scope, and description.
  • Assist with safe, logical file staging for grouping related changes and provide explicit safety rules to avoid secrets, destructive commands, and unsafe git config modifications.
  • Use Case: Prepare an organized commit for a feature change spanning several modules by auto-detecting scope, staging the relevant files, and producing a one-line description plus an explanatory body.

Quick Start

Create a conventional commit for the current working changes with intelligent staging and optionally override the suggested type, scope, or 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 git diffs automatically?

Generate conventional commit messages by analyzing repository diffs to infer the commit type and scope, producing Conventional Commits formatted text while safely staging related files.

What is the best way to stage related files logically before a git commit?

The best way to stage related files logically is using intelligent diff analysis to group changes, ensuring commits remain atomic and clear before applying safe git add operations.

Can I override the suggested commit type and scope during message generation?

Yes, you can interactively override the suggested commit type, scope, and description after the diff analysis infers initial values, allowing full control over the final Conventional Commits message.

How does automated commit generation handle sensitive data or destructive actions?

Automated commit generation applies explicit safety rules to avoid secrets, destructive commands, and unsafe git config modifications, performing only safe git add and git commit operations.

When do I need to use Conventional Commits format in my software repository?

You need the Conventional Commits format when standardizing commit history for clear traceability, infering commit types like feat or fix from changed files, and maintaining an organized repository.

Does git-commit work with unstaged files or only staged changes?

Git-commit works with both staged and unstaged files, analyzing repository diffs to assist with intelligent staging and grouping related changes before generating the commit message.