Semantic Atomic Commits
All substantive code, configuration, and architectural changes in this repository must be committed atomically and semantically.
Core Rules
- Atomic Commits:
- Each commit must encapsulate a single, discrete, and self-contained change.
- Avoid bundling unrelated changes or dirty working-tree edits into a single commit.
- Only stage the files directly associated with the specific change being committed (
git add <file>).
- Semantic Messages:
- Follow Conventional Commits formatting:
<type>(<scope>): <short description>.
- Common types:
feat, fix, docs, style, refactor, perf, test, chore.
- Write clear, imperative, concise summaries.
- Application:
- Apply this workflow after any substantive modification or feature completion.