commit

Generate bilingual Conventional Commits messages from staged changes and branch context.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often struggle to produce consistent, conventional commit messages across languages and branches. This Skill automates the generation of bilingual commit messages, ensuring standardized formatting for all changes.

Core Features & Use Cases

  • Generate Conventional Commit messages (feat, fix, docs, chore) based on staged changes.
  • Produce both English and Korean versions and save to commit_message.md for easy copy/paste.
  • Integrate with git workflows to infer issue numbers from branch names and provide suggested messages.

Quick Start

Stage your changes with git add, then invoke the commit skill to generate a bilingual Conventional Commit message and save it to commit_message.md.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate Conventional Commits messages for staged git changes?

To generate Conventional Commits messages, stage your changes with git add, then invoke the commit skill. It analyzes the staged changes and branch context to produce a bilingual commit message saved to commit_message.md.

Can I automatically infer issue numbers from a branch name for my commit message?

Yes, you can infer issue numbers from branch names. The commit skill integrates with your git workflow, analyzing branch context to automatically extract issue numbers and embed them into the generated Conventional Commits message.

How do I create bilingual English and Korean commit messages for git?

To create bilingual English and Korean commit messages, the commit skill analyzes your repository state and generates compliant messages in both languages, outputting them to a single commit_message.md file for easy copying.

Does the commit skill determine the correct Conventional Commits type like feat or fix automatically?

Yes, the commit skill determines the correct Conventional Commits type automatically. It analyzes your staged changes to infer whether the commit should be labeled feat, fix, docs, or chore based on the modifications.

What is the best way to standardize Conventional Commits formatting across a bilingual development team?

The best way to standardize Conventional Commits formatting across a bilingual team is automating message generation. The commit skill analyzes repository state and outputs standardized Korean and English messages to a markdown file.

Do I need to manually copy the generated bilingual commit message to my git workflow?

You need to copy the generated bilingual commit message from the saved commit_message.md file. The skill outputs the finalized English and Korean Conventional Commits message to this file for easy pasting into your git commit command.