Git Conventional Commit
Overview
Create one conventional commit per completed task while keeping the working tree clean and history stable.
Workflow
- •Review changes with
git statusandgit diff. - •Stage only the changes related to the task (use
git add -Aor selective adds). - •Compose a Conventional Commit message:
type(scope): summary.- •Types: feat, fix, refactor, docs, test, chore, build, ci, perf, style.
- •Use imperative mood and keep the summary under 72 characters.
- •Commit once per task. Do not amend, rebase, or rewrite history.
- •If there are no changes to commit, skip the commit and report why.
Notes
- •Avoid touching unrelated changes in a dirty working tree.
- •Prefer a specific scope (folder or subsystem) when it clarifies intent.