commit

Generate conventional git commit messages from current changes.

16|1|Updated Sep 24, 2025
One-click install
npx skills add https://github.com/Hey-Diga/dotclaude --skill commit-hey-diga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/Hey-Diga/dotclaude/tree/main/skills/commit
Command: npx skills add https://github.com/Hey-Diga/dotclaude --skill commit-hey-diga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating commits in the Conventional Commits format can be tedious and error-prone. This Skill automates generating git commit messages from current changes, ensuring consistent history and traceability.

Core Features & Use Cases

  • Generate conventional commit messages that include type, scope, description, and an optional issue reference, aligned with the Conventional Commits specification.
  • Analyze git status and diffs to determine the scope and changes to include in the commit.
  • Enforce formatting rules and output a ready-to-use commit message for git commit, with automatic branch-derived references when applicable.

Quick Start

Describe your changes or stage your files and instruct the skill to generate a conventional commit ready for git commit.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate a conventional commit message from git changes?

Generate conventional commit messages by parsing git status and diffs to derive type, scope, subject, and optional issue references. The tool analyzes current changes and enforces formatting rules to output a ready-to-use commit message aligned with the specification.

What is the conventional commits format and how does it enforce commit history?

The conventional commits format structures messages with type, scope, description, and issue references to ensure consistent history and traceability. It enforces strict type and subject formatting rules, automatically deriving issue references from the branch name when applicable.

Can I use this to create git commits for bug fixes and maintenance work?

Yes, you can create conventional git commits for feature work, bug fixes, and maintenance across any Git repository. It parses current diffs and applies the conventional commits format to generate appropriate commit messages for various types of changes.

How do I derive issue references from my branch name for a commit message?

Derive issue references from the branch name automatically when preparing commits. The tool parses the branch name to extract applicable issue references and includes them in the generated conventional commit message for better traceability.

What is the best way to automate conventional commit message generation?

Automate commit message generation by staging files and instructing the tool to analyze git status and diffs. It enforces type, scope, and subject formatting rules, then outputs a ready-to-commit message, eliminating manual formatting errors.