git-commit

Generate conventional Git commit messages from staged changes.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/VictorHueni/openAI-agentic-codebase-scaffold --skill git-commit-victorhueni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/VictorHueni/openAI-agentic-codebase-scaffold/tree/main/harness/workforce/agent-template/skills/git-commit
Command: npx skills add https://github.com/VictorHueni/openAI-agentic-codebase-scaffold --skill git-commit-victorhueni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of standardized, semantic Git commits, ensuring consistency and clarity in your project's history.

Core Features & Use Cases

  • Conventional Commits: Adheres to the Conventional Commits specification for structured commit messages.
  • Intelligent Staging: Analyzes changes to suggest or perform intelligent file staging.
  • Automated Message Generation: Generates commit messages based on code diffs, including type, scope, and description.
  • Interactive Mode: Allows for manual overrides of type, scope, and message for fine-grained control.
  • Use Case: After making several related changes to a feature, use this Skill to automatically generate a feat commit with an appropriate scope and description, ensuring your commit history is clean and informative.

Quick Start

Use the git-commit skill to commit the staged changes with an automatically generated conventional 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 conventional commit messages automatically from staged git changes?

The git-commit Skill analyzes staged git diffs to automatically detect and generate conventional commit messages. It identifies the appropriate commit type, scope, and description from your changes, ensuring your project history adheres to the Conventional Commits specification.

What is the best way to group related file changes into a single logical git commit?

Intelligent file staging analyzes your code changes to suggest or perform logical grouping for commits. This approach ensures related modifications are committed together, creating a clean and informative project history.

Can I manually override the commit type and scope when using automated message generation?

Yes, interactive mode allows you to manually override the commit type, scope, and message. This provides fine-grained control over your conventional commits while still leveraging automated diff analysis for the base description.

Does this automated git commit tool work without any external dependencies?

This automation operates without external dependencies, using only internal scripts and references to execute git commit operations. It directly analyzes staged changes to produce structured commit messages without requiring additional libraries.

Why should I use conventional commits instead of plain text git commit messages?

Using conventional commits provides structured, semantic information in your project history, making it easier to track changes and generate changelogs. Standardized types and scopes enhance clarity and consistency across your codebase.