Commit Changes

Overview

Analyze the current git changes, group related files into meaningful commits, and create clean git commits. Each commit should represent a single logical change and stage only the files that belong to that change.

Commit Message Standard

Use a short, one-sentence commit message with a conventional prefix.

Allowed Prefixes

• Feat: introducing a new feature or capability
• Fix: bug fixes or behavior corrections
• Refactor: code restructuring without behavior change
• Chore: tooling, config, or maintenance work
• Docs: documentation-only changes
• Test: adding or updating tests