git-commit

Name: git-commit
Availability: InStock
Author: akashic-devkit

Create Git commits following the Conventional Commits specification from code diffs.

2|1|Updated Sep 19, 2025

Search Tags:#git #developer tools #code review #version control #commit #conventional commits

Ready to run

npx skills add https://github.com/akashic-devkit/akashic-devkit --skill git-commit-akashic-devkit

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes 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 Analysis: Analyzes code diffs to suggest appropriate commit types and scopes.
Interactive Commit: Allows for interactive overrides of type, scope, and description.
Smart Staging: Intelligently stages files for logical grouping before committing.
Use Case: When you've finished a feature, use this Skill to generate a feat: commit message, automatically including the relevant files and a concise description based on your changes.

Quick Start

Use the git-commit skill to create a commit for the recent changes.

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

To generate conventional commit messages from git diffs, this Skill analyzes your code changes to determine the appropriate commit type, scope, and description based on the Conventional Commits specification. It intelligently stages relevant files and formats the semantic commit message.

What is the conventional commits format and how do I apply it to my git history?▼

The conventional commits format structures git history using semantic types like feat and fix. This Skill applies the specification automatically by analyzing your code diffs to generate structured commit messages with a type, scope, and concise description.

Can I override the suggested commit type and scope during an interactive git commit?▼

Yes, you can override the suggested commit type and scope during an interactive git commit. The Skill provides interactive override capabilities for commit message components, allowing you to manually adjust the semantic type, scope, and description before finalizing.

How do I stage files logically before creating a semantic git commit?▼

To stage files logically before creating a semantic git commit, this Skill features smart staging functionality that analyzes your changes and groups relevant files automatically. This ensures your commits contain cohesive modifications matching the generated message.

Does this automated commit tool work without manual staging?▼

Yes, the automated commit tool works without manual staging by utilizing smart staging features. It analyzes your code diffs and intelligently stages files for logical grouping, ensuring only relevant changes are included in the semantic commit output.

When should I not use automated conventional commit generation?▼

You should not use automated conventional commit generation when you need to bundle unrelated changes into a single commit or when your project does not follow the Conventional Commits specification. The tool focuses on semantic accuracy and logical file grouping for clear history.