git-commit

Generates conventional commit messages by analyzing git diffs and staging changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, meaningful commit messages is tedious and often inconsistent across a team. This Skill analyzes your actual code changes and produces standardized Conventional Commits messages with the correct type, scope, and description. ## Core Features & Use Cases - Diff-Based Message Generation: Inspects staged or working-tree diffs to auto-detect the commit type (feat, fix, docs, refactor, etc.) and affected scope. - Intelligent Staging: Groups and stages files logically so each commit represents one coherent change. - Breaking Change Support: Formats breaking changes with the ! marker or BREAKING CHANGE footer per the Conventional Commits specification. - Use Case: After finishing a bug fix across three files, ask for a commit and receive a properly formatted message like fix(auth): correct token expiry validation without writing it yourself. ## Quick Start Ask the assistant to commit my current changes with a conventional commit message based on the diff.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I write a conventional commit message?

A conventional commit follows the format type(scope): description, using types like feat, fix, docs, refactor, or test. This Skill analyzes your git diff to pick the right type and scope, then writes the description in present tense under 72 characters.

How to generate a commit message from git diff automatically?

The Skill runs git diff --staged or git diff to inspect actual changes, determines the appropriate type and scope from the modified files, and executes git commit with the generated message. No manual message writing is needed.

How do I mark a breaking change in conventional commits?

Add an exclamation mark after the type or scope, like feat!: remove deprecated endpoint, or include a BREAKING CHANGE footer in the commit body explaining what behavior changed.

Can it prevent committing secrets or sensitive files?

Yes, the workflow explicitly warns against committing secrets such as .env files, credentials.json, or private keys during the staging step. It also enforces git safety rules like never force-pushing to main or skipping hooks without permission.

What happens if a pre-commit hook fails?

If a commit fails due to hooks, the guidance is to fix the underlying issue and create a new commit rather than amending or bypassing the hook with --no-verify. Hooks are only skipped when the user explicitly requests it.