git-commit

Analyze code diffs to generate conventional Git commit messages.

1|Updated May 4, 2026
One-click install
npx skills add https://github.com/beel-collab/presets.dev --skill git-commit-beel-collab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/beel-collab/presets.dev/tree/main/skills/git-commit
Command: npx skills add https://github.com/beel-collab/presets.dev --skill git-commit-beel-collab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill simplifies creating standardized, semantic Git commits by analyzing diffs, auto-detecting type and scope, and composing conventional messages for teams. It reduces manual drafting and ensures consistent history across repositories.

Core Features & Use Cases

  • Auto-detects type and scope from changes and suggests a conventional commit format.
  • Generates commit messages from diffs with optional overrides for type, scope, and description.
  • Interactive staging and commit workflow to group related changes into logical commits.
  • Works with standard Git workflows to maintain clean, readable history across branches and PRs.
  • Use Case: A feature branch contains multiple unrelated changes; this Skill helps produce focused commits with meaningful messages.

Quick Start

Ask the AI to create a conventional commit for your staged changes and provide the exact git commit command to run, e.g., "feat(core): add authentication hook" and then execute the suggested command.

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 automatically?

To generate conventional commit messages from git diffs, this Skill analyzes staged code changes, auto-detects the type and scope, and suggests a formatted message. It ties the generated semantic text directly to the code diffs to maintain readable history.

What is the best way to split unrelated changes into focused git commits?

The best way to split unrelated changes into focused git commits is using the Skill's interactive staging workflow. It groups related changes logically, allowing you to produce focused conventional commits with meaningful messages for each distinct update.

Can I override the auto-detected type and scope for a conventional commit?

Yes, you can override the auto-detected type and scope for a conventional commit. The Skill generates a commit message from your diff and provides optional overrides, letting you manually specify the type, scope, and description to fit your team's standards.

Does this conventional commit generator work with standard version-control workflows?

This conventional commit generator works directly with standard version-control workflows. It integrates with regular Git commands and helps maintain clean, readable history across your branches and pull requests without disrupting your existing process.

How do I craft a conventional commit command after staging my changes?

To craft a conventional commit command after staging changes, ask the AI to generate the message and provide the exact Git command to run. You then execute the suggested command, such as feat(core): add authentication hook, to finalize the commit.