skills.rest
kubrickcode
kubrickcodeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit

Generates Conventional Commits-compliant messages in Korean and English from staged git changes.

1|Updated Mar 8, 2026
Search Tags:#git#changelog#code review#version control#conventional commits#commit message#korean
One-click install
npx skills add https://github.com/kubrickcode/cine-mirror --skill commit-kubrickcode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/kubrickcode/cine-mirror/tree/main/.agents/skills/commit
Command: npx skills add https://github.com/kubrickcode/cine-mirror --skill commit-kubrickcode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, meaningful commit messages is tedious and often results in vague history. This Skill analyzes your staged git changes and produces well-structured Conventional Commits messages in both Korean and English, saved to a file for easy copying. ## Core Features & Use Cases - Conventional Commits Compliance: Generates messages following the Conventional Commits v1.0.0 specification with proper types (feat, fix, docs, chore, etc.) and optional scopes. - Automatic Issue Linking: Detects issue numbers from branch names (e.g., develop/shlee/32) and appends "fix #N" footers automatically. - Purpose-Driven Messages: Enforces narrative-style bodies that explain why a change was made rather than listing technical modifications, with self-verification gates. - Use Case: After staging changes on a feature branch, invoke the Skill to receive a commit_message.md file containing both Korean and English message candidates with the suggested type and reasoning. ## Quick Start Generate a Conventional Commits message for my currently staged git changes 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 a Conventional Commits message for staged changes?▼

Stage your changes with git add, then invoke the Skill. It runs git status, diff, and log to analyze the changes, selects the appropriate type (feat, fix, docs, etc.), and writes Korean and English message versions to commit_message.md.

What is the difference between fix, ifix, and chore commit types?▼

Use fix for user-facing bugs, ifix for internal infrastructure bugs like CI or build failures, and chore for dependency updates and tooling changes. The key distinction is whether the issue affects end users or only developers and infrastructure.

Does this Skill automatically commit my changes?▼

No, it only generates commit messages and saves them to commit_message.md. You must manually copy your preferred Korean or English version and run git commit yourself.

How does the commit message include issue numbers automatically?▼

The Skill parses the current branch name for a trailing number, such as develop/shlee/32, and appends a "fix #32" footer to the generated message. This links the commit to the corresponding issue tracker item.

Why should commit messages describe purpose instead of technical changes?▼

Commit messages serve as project history that explains why a change was needed, not what code was modified. The git diff already shows technical changes, so the message should provide context about the problem solved and the rationale for the approach.

Related Skills

Explore More Software Engineering Skills→
cattboycattboy

commit

Stage changes and commit with conventional messages enriched by GitHub context.

Community
Intermediate
eriknovakeriknovak

commit-pr

Create a conventional commit, push the branch, and open a GitHub pull request.

Community
Advanced
pandaworks-software-pltpandaworks-software-plt

hermes-commit

Verify code review and lint checks, then execute atomic commits.

Official
Advanced
fartmonarchfartmonarch
1

chinese-commit-conventions

Standardize Chinese Git commit messages and changelog configuration.

Community
Intermediate