Git 커밋 메시지 생성기

Conventional Commits is a specification for writing commit messages that provides a consistent format for automated tools and easier understanding of changes. Each commit message follows the structure: type(scope): description. Common types include feat (new feature), fix (bug fix), docs (documentation), style (formatting), refactor (code refactoring), perf (performance), test (tests), chore (maintenance), build (build system), ci (CI configuration), and revert (revert a commit).

Select a commit type from the available options (feat, fix, docs, etc.). Optionally add a scope to indicate which part of the codebase is affected (e.g., auth, components, api). Write a clear, imperative mood subject line describing what the commit does and why. Optionally add a detailed body explaining the change more thoroughly. For breaking changes, check the Breaking Change box. Click Generate to create your commit message, then Copy to use it in your Git workflow.

Use imperative mood ("add feature" not "added" or "adds"). Keep the subject line under 72 characters. Explain what and why, not how. Reference issues in the footer (e.g., Closes #123). For breaking changes, start the body or footer with "BREAKING CHANGE: ". Be consistent across your project.