commit-changes

When committing changes, follow this workflow:

This skill creates ordinary, new commits from reviewed staged changes only. It must never create a merge commit or squash commits: do not run git merge, git merge --no-ff, git merge --squash, git rebase --autosquash, git commit --amend to fold commits together, or any equivalent history-combining operation.

1. Analyze the workspace: Run git status and git diff (staged and unstaged) to understand all changes.

2. Group changes semantically: Identify logical units of work. Each commit must be atomic — one functional change per commit. Group related files that together implement a single concern.