git-commit

Name: git-commit
Availability: InStock
Author: andreicr1

Generate conventional git commit messages for staged and unstaged changes.

Updated Mar 14, 2026

Search Tags:#git #workflow #commit #command-line #version-control #conventional-commits

Ready to run

npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill git-commit-andreicr1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/Andreicr1/netz-analysis-engine/tree/main/.gemini/skills/git-commit
Command: npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill git-commit-andreicr1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing meaningful Git commit messages is time-consuming and error-prone; this skill streamlines crafting concise, conventional messages that communicate intent and rationale.

Core Features & Use Cases

Generate subject lines following conventional commits or project-specific conventions.
Handle both staged and unstaged changes and apply optional body with rationale.
Adapt to repository conventions when available and group related changes into a single commit when appropriate.

Quick Start

Create a clear, conventional git commit message for the current changes.

Frequently Asked Questions about git-commit

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

FAQPage Schema

How do I write conventional commit messages for staged and unstaged git changes?▼

Conventional commit messages are automated by generating a concise subject line, an optional body with rationale, and grouping related repository changes into a single, safe commit command. This applies to both staged and unstaged updates.

What is the best way to automate git commit message creation for repository changes?▼

Automating git commit message creation applies conventional commit formats or project-specific conventions to generate a concise subject line and optional rationale body, safely grouping related changes into a single commit command.

Can I use project-specific commit conventions instead of standard conventional commits?▼

Yes, you can use project-specific commit conventions. The automation adapts to available repository conventions, allowing you to follow project-specific formats instead of standard conventional commits for your version-control workflow.

Does this git commit workflow handle both staged and unstaged changes?▼

Yes, this git commit workflow handles both staged and unstaged changes. It analyzes current repository updates, applies controlled grouping of related changes, and generates a single, safe commit command with a meaningful message.

When should I group related git changes into a single commit?▼

You should group related git changes into a single commit when repository updates share the same intent and rationale. The automation applies controlled grouping to ensure the conventional commit message accurately communicates the combined scope.