올클 커밋 생성 가이드

To divide git commits logically, group changes by meaning such as features, refactoring, tests, docs, and chores into separate commit-sized units. This process reads git status and diffs to exclude unrelated files, preserving clean commit boundaries for each logical unit.

Korean git commit messages follow a strict type summary convention formatted as type: 한국어 요약. This format avoids unnecessary English expressions and generates concise Korean summaries, ensuring consistent commit message conventions across the repository.

Before creating a git commit, run git status and git diff to inspect all changes, then verify the staged diff to ensure only intended files are included. This pre-commit procedure preserves clean commit boundaries and helps exclude unrelated files from the current commit.

Yes, you can separate refactoring and feature changes into different git commits by reviewing branch diffs and staging decisions. The commit division process distinguishes features, refactors, tests, docs, and chores as separate logical units, maintaining strict boundaries between unrelated changes.

Files not included in a git commit should be reported and reviewed in subsequent staging decisions. The commit generation process explicitly reports what was excluded, allowing you to verify that unrelated files remain unstaged for future logical commit units.

Git commits contain unrelated changes when staging decisions fail to separate features, refactors, tests, and docs into distinct units. Reviewing git diff before staging and applying logical commit boundaries prevents mixing unrelated files within a single commit.