git-githublisted

# Git and GitHub Workflow Skill Comprehensive guide for Git version control and GitHub collaboration patterns. ## When This Activates - Creating commits or branches - Opening or reviewing pull requests - Managing GitHub issues - Using the gh CLI - Keywords: "git", "github", "commit", "branch", "pr", "pull request", "merge", "issue" --- ## Conventional Commits All commit messages follow the conventional commits specification: ``` <type>(<scope>): <description> [optional body] [optional footer(s)] ``` ### Types | Type | When to Use | |------|-------------| | `feat` | New feature or capability | | `fix` | Bug fix | | `docs` | Documentation only changes | | `style` | Formatting, missing semicolons, etc. | | `refactor` | Code change that neither fixes a bug nor adds a feature | | `perf` | Performance improvement | | `test` | Adding or correcting tests | | `chore` | Build process, auxiliary tools, or maintenance | | `ci` | CI/CD configuration changes | ### Examples ```bash feat(auth): add JWT token refresh endpoint fix(api): handle null response from upstream service docs: update API reference for v2 endpoints refactor(db): extract query builder into separate module test(auth): add integration tests for OAuth flow chore: upgrade dependencies to latest versions ``` ### Breaking Changes Use `!` after type or add `BREAKING CHANGE:` footer: ```bash feat(api)!: change response format from XML to JSON ``` --- ## Branch Naming Conventions ``` <type>/<issue-number>-<shor