git-commit

Generate conventional git commit messages from repository status and diffs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/xbpk3t/ce-codex --skill git-commit-xbpk3t
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/xbpk3t/ce-codex/tree/main/skills/git-commit
Command: npx skills add https://github.com/xbpk3t/ce-codex --skill git-commit-xbpk3t

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the uncertainty and time spent crafting commit messages and making commits that follow repository conventions, helping maintainers and collaborators understand the intent and scope of changes.

Core Features & Use Cases

  • Convention detection: Infer commit message style from documented rules or recent commit history and default to conventional commits when no pattern exists.
  • Context-aware commits: Use working tree diff, git status, current branch, and recent commits to decide staging, branch creation, and message content.
  • Safe staging and confirmation: Group changes at the file level into logical commits, stage selected files, create feature branches when appropriate, and verify success by reporting commit hashes and git status.

Quick Start

Create a single, well-structured git commit from your current working tree changes following the repository's commit conventions.

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?

Generate conventional commit messages by analyzing git working tree diffs and status to infer project conventions, then producing structured subject lines and optional bodies following detected formatting rules.

Can I stage specific files and split changes into multiple git commits?

Stage specific files and split changes into multiple git commits by grouping working tree modifications at the file level into logical commits, staging selected files, and running git commit sequentially.

How does convention detection work for git commit messages?

Convention detection for git commit messages works by inferring commit style from documented rules or recent commit history, defaulting to conventional commits when no existing pattern is found in the repository.

What is the best way to create feature branches and commit changes automatically?

Create feature branches and commit changes automatically by analyzing the working tree diff and current git status, optionally creating a feature branch, staging selected files, and verifying success by reporting commit hashes.

Does this git commit tool work with local git repositories only?

This git commit tool works with local git repositories to stage files, analyze working tree diffs, create feature branches, and verify commit success by reporting updated git status and commit hashes.

Why should I use automated conventional commits instead of manual staging?

Automated conventional commits remove the uncertainty of manual staging by analyzing working tree diffs to generate convention-aware commit messages, helping maintainers and collaborators understand the intent and scope of changes.