commit

Generate Conventional Commits messages for staged changes with user confirmation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates the generation of standardized git commit messages for changed files, ensuring consistency with the Conventional Commits format and reducing manual writing.

Core Features & Use Cases

  • Proposes conventional commit messages based on staged changes and lets you review/edit before committing.
  • Supports a three-way confirmation flow: Accept to commit, Edit to customize, Cancel to abort.
  • Fits typical software development workflows requiring clear, consistent commits (features, fixes, chores).

Quick Start

Review the proposed commit message and choose to Accept, Edit, or Cancel.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commit messages for staged git changes?

To generate conventional commit messages, the Skill analyzes your staged git changes and proposes a formatted message. You can then review the generated commit message and choose to accept, edit, or cancel before finalizing the commit.

What is the Conventional Commits format and why use it for git workflow automation?

The Conventional Commits format is a standardized structure for git commit messages that ensures clear history tracking. Using it for git workflow automation reduces manual writing effort and enforces consistency across features, fixes, and chores.

Can I review and edit a generated commit message before committing?

Yes, you can review and edit a generated commit message before committing. The workflow uses a three-way confirmation flow, allowing you to accept the proposal to commit, edit to customize the text, or cancel to abort the action.

Do I need to manually add a Co-Authored-By trailer when generating commits?

You do not need to manually add a Co-Authored-By trailer. The commit generation process includes an optional force flag that can automatically bypass granularity checks and include the Co-Authored-By trailer in the final message.

What's the best way to enforce commit message consistency across a software development team?

The best way to enforce commit message consistency is to automate generation using the Conventional Commits format. This ensures all changed files follow the same standardized structure for features, fixes, and chores before user confirmation.