commit

Analyze the Git staging area and generate a conventional commit message.

Updated Dec 21, 2021
One-click install
npx skills add https://github.com/dobraga/dotfiles --skill commit-dobraga
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/dobraga/dotfiles/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/dobraga/dotfiles --skill commit-dobraga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes staged changes and crafts a high-quality conventional commit message, then applies the commit to the repository.

Core Features & Use Cases

  • Atomic commits: ensures changes can be committed as a single coherent unit.
  • Conventional type & scope: derives type (feat, fix, docs, etc.) and appends an optional breaking change footer when needed.
  • Audit & guardrails: validates atomicity and prompts for splitting changes if needed to maintain clean history.

Quick Start

To commit with a clean, conventional message, run the skill when you have staged changes ready to 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 from staged changes?

To generate a conventional commit from staged changes, this Skill analyzes your Git staging area to classify change type and scope, then applies a standardized commit message format automatically.

What is an atomic commit and how does it enforce single-idea commits?

An atomic commit packages a single coherent unit of work. This Skill enforces atomicity by validating staged changes and prompting you to split them if multiple unrelated ideas are detected.

Can I automatically add breaking change footers to conventional commits?

Yes, you can automatically add breaking change footers to conventional commits. The Skill derives the type and scope, appending the required breaking change footer when needed.

What is the best way to handle mixed staged changes before committing?

The best way to handle mixed staged changes is to run an atomicity check. This Skill audits your staging area and prompts you to split changes to maintain a clean, coherent Git history.

Does this commit automation work without manual message input?

Yes, this commit automation works without manual message input. It analyzes the Git staging area, determines the appropriate conventional-commit message, and executes the commit directly.

When should I avoid using automated conventional commit generation?

You should avoid using automated conventional commit generation when your staged changes mix unrelated features or fixes, as the Skill's atomicity guardrails will prompt you to split them first.