smart_commit_skill

Overview

This skill generates intelligent commit messages that follow the Conventional Commits convention and reflect actual git changes. It is context-aware and produces commit subjects and optional bodies in Korean, based on the diff and modified files. The goal is concise, actionable commit messages that fit project rules and improve changelog quality.

How this skill works

The skill inspects the provided git diff or list of modified files to identify the primary intent of the change (feat, fix, docs, style, refactor, test, chore). It constructs a concise subject line in Korean using the Conventional Commits format (type: subject) and adds an optional Korean body when additional explanation is needed. The generated message strictly reflects the code changes and avoids vague or irrelevant content.

When to use it

• When committing code to ensure messages follow Conventional Commits and project language rules
• During pull request creation to provide a clear, standardized commit subject in Korean
• When generating changelogs or release notes that rely on structured commit types
• For automated commit message suggestions in CI or developer tools
• When multiple contributors must adhere to a shared commit format and language

Best practices

• Always base the message on the actual git diff or file changes, not assumptions
• Choose the single primary type that best describes the change; keep subjects concise
• Write the subject in present tense and limit it to a short summary in Korean
• Add a short Korean body only for clarifying intent, scope, or migration steps
• Avoid vague or English-only subjects; be explicit about the purpose of the change

Example use cases

• A new API endpoint is added: generate a Korean feat subject that names the feature
• A crash fix is implemented: produce a Korean fix subject describing the issue resolved
• Documentation updates: create a docs subject that specifies which file or section changed
• Code style reformatting: use a style subject noting the formatter or lint rule applied
• Refactoring without behavior change: emit a refactor subject naming the refactored module