git-workflow

# Git Workflow ## Instructions ### Step 1: Identify the Task Determine which workflow the user needs: 1. **Commit message** - writing or improving a commit message 2. **Branching strategy** - choosing or implementing a branching model 3. **Conflict resolution** - resolving merge conflicts 4. **Changelog** - generating release notes from commit history Ask clarifying questions only if the intent is ambiguous. ### Step 2: Conventional Commits When writing commit messages, follow the Conventional Commits specification: ``` <type>[optional scope]: <description> [optional body] [optional footer(s)] ``` **Types (in order of frequency):** - `feat` - new feature (correlates with MINOR in semver) - `fix` - bug fix (correlates with PATCH in semver) - `docs` - documentation only - `style` - formatting, no code change - `refactor` - neither fix nor feature - `perf` - performance improvement - `test` - adding or fixing tests - `chore` - build process, tooling, dependencies - `ci` - CI/CD configuration changes **Rules:** - Description is lowercase, no period at end, max 72 characters - Body wraps at 72 characters, explains what and why (not how) - Breaking changes: add `!` after type or `BREAKING CHANGE:` in footer **Examples:** ``` feat(auth): add OAuth2 login with Google provider Implements the OAuth2 authorization code flow for Google. Stores tokens in encrypted session storage. Closes #142 ``` ``` fix(api): prevent race condition in concurrent order creation Added optim...