git-commit

Generate conventional commit messages from git diffs and stage related files.

Updated Aug 23, 2026

Search Tags:#git #staging #commit-message #conventional-commits #diff-analysis

Ready to run

npx skills add https://github.com/Berkay2002/skills --skill git-commit-berkay2002

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/Berkay2002/skills/tree/main/skills/git-commit
Command: npx skills add https://github.com/Berkay2002/skills --skill git-commit-berkay2002

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates creating standardized Conventional Commit messages and intelligently staging related files so developers no longer write ad-hoc commit messages or incorrectly group changes.

Core Features & Use Cases

Automatic Message Generation: Analyze diffs to infer commit type, optional scope, and a concise imperative description that follows Conventional Commits.
Intelligent Staging: Recommend or perform selective staging to group logically related changes and support interactive staging workflows.
Use Case: When a feature touches multiple modules, stage the relevant files together and produce a single semantic commit that documents the change and references issues.

Quick Start

Commit all current changes using conventional commit rules and propose a type, scope, and description based on the repository diff.

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?▼

Generating conventional commit messages from git diffs requires analyzing staged or unstaged changes to infer the commit type, optional scope, and a concise imperative description that adheres to Conventional Commits specifications.

What are conventional commits and when do I need them for my git repository?▼

Conventional commits are a standardized message format used to document changes in a git repository. You need them to automate changelog generation and clearly communicate the type and scope of changes applied to your codebase.

How do I stage related files together and create a single semantic git commit?▼

Staging related files together for a semantic git commit requires intelligent selective staging that groups logically related changes, supporting interactive workflows to ensure a single clean conventional commit message.

Can I override the inferred commit type and scope when generating a commit message?▼

Yes, you can override the inferred commit type and scope. Message generation from diffs supports optional user overrides, allowing you to manually specify the type, scope, and description instead of using the inferred values.

How do I avoid accidentally committing secrets when staging git changes?▼

Avoiding committing secrets when staging git changes requires adherence to safety rules that scan repository diffs and block the inclusion of sensitive information before generating the final commit message.