commit

Generates bilingual English and Tagline-compliant commit messages from staged Git changes.

1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/kubrickcode/specvital --skill commit-kubrickcode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/kubrickcode/specvital/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/kubrickcode/specvital --skill commit-kubrickcode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of well-structured commit messages that adhere to the Conventional Commits specification, ensuring consistency and clarity in your project's version history.

Core Features & Use Cases

  • Automated Commit Message Generation: Creates messages in both Korean and English based on staged changes.
  • Conventional Commits Compliance: Enforces a standardized format for types (feat, fix, docs, etc.), scope, description, body, and footers.
  • Contextual Analysis: Analyzes git status, diff, branch name, and recent logs to inform message generation.
  • Use Case: After making several bug fixes, use this Skill to generate a commit message like fix(api): resolve authentication issue for user login with a detailed explanation of the root cause and solution.

Quick Start

Use the commit skill to generate a conventional commit message for your staged changes.

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 for staged Git changes, this Skill analyzes your repository status, diff, and branch name to suggest appropriate commit types like feat or fix, along with a structured description and message body.

What is the conventional commits format and when do I need it for version control?

The conventional commits format standardizes version control history by structuring messages with specific commit types, scope, and description. You need it to ensure consistency and clarity in your project history, making it easier to track features, fixes, and breaking changes.

Can I create conventional commit messages in both Korean and English?

Yes, you can create conventional commit messages in both Korean and English. The Skill automatically generates compliant messages in both languages based on your staged Git changes, supporting standardized formatting across multilingual development teams.

Does the commit message generator analyze git diff and branch name context?

Yes, the commit message generator analyzes git diff and branch name context. It examines your repository status, staged diff, and branch name to inform the generated message structure, ensuring the suggested commit type and description accurately reflect the actual changes.

What's the best way to automate code review commit messages for bug fixes?

The best way to automate code review commit messages for bug fixes is using a conventional commits generator that analyzes your staged diff to produce standardized messages, including detailed message bodies explaining the root cause and implementation rationale.