commit-changes

When committing changes, follow this workflow:

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.

3. Write conventional commit messages: Use the format <type>(<scope>): <description> without a body. Allowed types:

   • feat: new feature
   • fix: bug fix
   • refactor: code restructuring without behavior change
   • docs: documentation only
   • style: formatting, whitespace, semicolons (no logic change)
   • test: adding or updating tests
   • chore: tooling, configs, dependencies
   • perf: performance improvement
   • ci: CI/CD changes
   • build: build system changes
   • revert: reverting a previous commit