semantic-commitlisted

# Semantic Commit Split work-in-progress changes into clean, reviewable conventional commits, verifying before each commit. ## Applicability Use when: - Multiple unrelated changes are unstaged/staged together - User asks for "semantic commits", "logical commits", or "커밋 분리" - After a multi-item implementation session before pushing Skip when: - There is only one logical change (just commit it directly) - User explicitly asks for a single combined commit ## Steps ### 1. Understand the Full Diff Run in parallel: ```bash git status git diff HEAD git diff --cached ``` Read each changed file if the diff alone is insufficient to determine intent. Treat the existing index as owned work. Do not reset, unstage, or replace it without explicit approval. ### 2. Group by Concern Assign each changed file to a group: | Type | When | | ----------------- | ------------------------------------------- | | `feat(scope)` | New user-facing behavior | | `fix(scope)` | Bug correction | | `perf(scope)` | Performance improvement, no behavior change | | `refactor(scope)` | Code restructure, no behavior change | | `test(scope)` | Test additions or changes only | | `build(scope)` | Build system, deps, bundler, packaging | | `ci(scope)` | CI/CD config and pipelines | | `chore(scope)` | Tooling, version bump, misc maintenanc