--- name: github-workflow-best-practices description: Master GitHub workflows including branching strategies, commit standards, PR processes, issue triage, sprint management, and git worktree usage. Activate when planning GitHub workflows, managing sprints, or establishing team conventions. triggers: - "github workflow" - "PR best practices" - "github branching" - "sprint management" - "commit message" - "git worktree" - "github standards" - "issue triage" - "conventional commits" --- # GitHub Workflow Best Practices Master professional GitHub workflows that scale from solo projects to large teams. This skill covers branching strategies, commit conventions, PR processes, issue management, sprint execution, and advanced git worktree patterns. ## Branching Strategy ### Branch Naming Conventions Follow a consistent naming pattern that communicates intent: ``` /- Examples: feature/123-user-authentication bugfix/456-login-redirect hotfix/789-security-patch chore/update-dependencies docs/api-documentation ``` **Branch Types**: - `feature/` - New functionality - `bugfix/` - Bug fixes - `hotfix/` - Urgent production fixes - `chore/` - Maintenance tasks (dependencies, config) - `docs/` - Documentation updates - `refactor/` - Code refactoring without behavior change - `test/` - Test additions or updates ### Branch Lifecycle **Main Branches**: - `main` (or `master`) - Production-ready code - `develop` - Integration branch for features (optional) **Feature Branch Flow**: ``` 1. Create branch from main 2. Develop and commit 3. Push to remote 4. Create PR 5. Code review 6. Merge to main 7. Delete branch 8. Clean up local/remote ``` **Protection Rules**: - Require PR reviews before merge - Require status checks to pass - Require branches to be up to date - Restrict force pushes - Restrict deletions See [Branching Strategy Details](references/branching-strategy.md) for advanced patterns. ## Commit Message Standards ### Conventional Commits Format Use the conventional commits specification for clarity and automation: ``` ():