git-workflow-enforcerlisted

# Git Workflow Enforcer Enforces consistent Git workflows including commit messages, branch naming, and PR processes. ## When to Use - Creating commits or branches - Code review or PR creation - User mentions "git workflow", "commit message", "branch naming", or "pull request" ## Instructions ### 1. Detect Existing Conventions Check for: - `.github/` or `.gitlab/` templates - `CONTRIBUTING.md` - Existing commit message patterns - Branch naming patterns ### 2. Conventional Commits **Format:** `type(scope): description` **Types:** - `feat`: New feature - `fix`: Bug fix - `docs`: Documentation - `style`: Formatting, missing semicolons - `refactor`: Code restructuring - `perf`: Performance improvement - `test`: Adding tests - `chore`: Maintenance, dependencies **Examples:** ``` feat(auth): add OAuth2 login support fix(api): handle null response in user endpoint docs(readme): update installation instructions refactor(utils): simplify date formatting logic ``` ### 3. Branch Naming **Common patterns:** ``` feature/user-authentication bugfix/login-error-handling hotfix/critical-security-patch release/v1.2.0 chore/update-dependencies ``` **Validate:** - Lowercase with hyphens - Prefixed with type - Descriptive name - Issue number if applicable: `feature/123-add-dark-mode` ### 4. Commit Message Validation **Good commit:** ``` feat(payments): integrate Stripe payment gateway - Add Stripe SDK configuration - Implement payment intent creation - Add webhook handler for payme