Toolditor Readable Commits

Overview

Build a clean commit stack without changing implementation behavior. Favor explicit file-by-file staging, coherent scope boundaries, and Korean commit messages that pass .husky/commit-msg.

Non-Negotiable Rules

1. Do not change code logic just to reorganize commits.
2. Do not use destructive git commands (reset --hard, checkout --, stash manipulation) unless explicitly requested.
3. Respect commit convention:

• header: [type] message (Korean message)
• body: optional flat bullet list (- 설명)

4. Keep commit scopes independent so each commit is reviewable and revertable.
5. Verify commit list after every 1-2 commits, not only at the end.
6. Run npm run check before starting split work; if it fails, fix lint/type errors first.
7. Do not bypass verification for delivery: never use --no-verify for pushes.
8. Do not isolate docs into docs-only commits when they explain code changes in the same stack; attach docs to the related commit.