github-workflow

Automate GitHub issue tracking and branch creation by using the gh CLI to view issues and creating branches from main with conventional prefixes like feat/, fix/, chore/, or refactor/. This guided workflow reduces miscommunication by clarifying roles and steps for collaborative development.

The conventional branch naming format for GitHub pull requests uses prefixes such as feat/, fix/, chore/, or refactor/ branched directly from main. Branches should include issue references when applicable to maintain clear tracking throughout the development workflow.

Write a conventional commit PR title for merging by using a single-line message with proper scope and no body text. The PR body should include closing references like "closes #123" and relevant checks must pass before merging.

Yes, you need gh CLI to manage GitHub issues and PRs effectively within this workflow. The Skill specifies using gh CLI specifically for issue viewing to verify bug reproduction and understand expected behavior before creating branches.

The best way to prepare a GitHub PR for merge review is to use conventional-commit-style titles, include closes references in the PR body notes, and run all relevant checks before merging. This ensures proper issue tracking and code quality.

Your GitHub workflow needs conventional commit guidelines to reduce miscommunication and errors in collaborative development. Single-line conventional messages with proper scope ensure consistent history, while structured PR titles and branch prefixes maintain clarity across issues and merges.