Automated Git Commits

This skill provides instructions for performing atomic, well-structured Git commits following the Conventional Commits specification.

1. Analyze Changes

• Identify Modified Files: Run git status --short to see all staged and unstaged changes.
• Respect Ignore Rules: Do NOT include files that the user has explicitly requested to ignore or that match .gitignore patterns.
• Group by Scope: Group modified files by their logical "scope" (e.g., a specific module, feature, or layer like data, domain, ui).

2. Branching

• Feature Branches: ALWAYS create descriptive feature branches from main (e.g., feat/login-logic).
• Merge Flow: Merge back into main only after passing all quality checks and PR approval.