git-managerlisted

# Git Workflow Patterns Comprehensive git workflow guidance covering branch management, commit conventions, pull request best practices, conflict resolution, and LazyGit integration. Emphasizes clean history, collaboration patterns, and the user's established branch naming conventions. ## When This Skill Applies Use this skill when: - Creating or managing branches - Writing commit messages - Preparing pull requests - Resolving merge conflicts - Reviewing code changes - Collaborating with team - Questions about git best practices - Using LazyGit for version control ## Branch Naming Strategy ### Standard Prefixes **Core Development**: - `feat/` - New features (user-facing or API) - `enhance/` - Improvements to existing features (not bugs) - `fix/` - Bug fixes - `hotfix/` - Critical production fixes **Code Quality**: - `refactor/` - Code restructuring (no behaviour change) - `types/` - Type definitions (interfaces, types, contracts) - `perf/` - Performance improvements - `test/` - Adding/updating tests - `debug/` - Debugging/investigation branches (temporary) **Documentation & Content**: - `docs/` - Documentation changes - `content/` - Content updates (copy, text, data files) **Styling & UI**: - `styles/` - Visual styling (colors, fonts, spacing) - `layout/` - Structural positioning (grid, flexbox, responsive) - `a11y/` - Accessibility improvements **Dependencies & Configuration**: - `deps/` - Dependency updates - `build/` - Build system, bundler, tooling - `config/` -