conventional-commit

To generate conventional commit messages with Korean descriptions, you provide your changes and the skill outputs standardized messages using English types like feat or fix, optional scope, and Korean description and body text.

The conventional commits format structures git commit messages using a specific type, an optional scope, a description, a body, and a footer to produce clear, machine-readable release notes and improve traceability.

Yes, you can use English types and scopes with Korean body text in a git commit. The skill enforces language guidelines requiring English for types and scopes, Korean for descriptions and bodies, and bilingual footer keywords.

You prepare release notes from conventional commit messages by applying the specification's structured format, which uses bilingual footer keywords to produce clear, machine-readable outputs suitable for release-note preparation.

The best way to automate standardized git commit message generation is to input your changes and let the skill automatically format them into the conventional commits specification with correct types, scopes, and descriptions.

No, you do not need any dependencies to create conventional commits with this skill, as it operates independently without requiring external components or modules to generate the standardized messages.