git-patternslisted

# Git Patterns ## When to load this skill - User asks about commit message format, rebase, squash, or fixup - User asks about branch naming or branch strategy - User asks about recovering lost commits or undoing changes - User is resolving merge conflicts - User asks about git bisect, worktrees, or stash ## When not to load this skill - GitHub Actions or CI pipeline configuration - GitOps / infrastructure deployment pipelines --- ## Conventional Commits Conventional Commits give machines and humans a consistent way to parse commit history and derive semver bumps. ### Format ``` <type>[optional scope]: <description> [optional body] [optional footer(s)] ``` ### Types and semver mapping | Type | SemVer bump | When to use | | ---------- | ----------- | ------------------------------------ | | `feat` | MINOR | New user-facing feature | | `fix` | PATCH | Bug fix | | `docs` | none | Documentation only | | `style` | none | Formatting, no logic change | | `refactor` | none | Code restructure, no behavior change | | `perf` | none | Performance improvement | | `test` | none | Adding or fixing tests | | `chore` | none | Build tooling, dependency updates | | `ci` | none | CI configuration | ### Breaking changes Two equivalent ways to