git-workflow

Branch-based workflows enforce structured collaboration by requiring feature branches with conventional prefixes (feat/, fix/, docs/) and mandatory draft pull requests before merging non-trivial changes. This reduces integration surprises and standardizes code review processes across your team.

Conventional commits use prefixes like feat/, fix/, and docs/ to categorize changes at a glance. This naming convention clarifies intent, automates changelog generation, and helps teams quickly understand what each branch addresses without reading commit messages.

Create a feature branch using git checkout -b feat/description, then push with git push -u origin feat/description. Open a draft PR immediately after your initial commit using gh pr create --draft to signal work-in-progress and invite early feedback before marking it ready for review.

Use draft PRs for non-trivial changes after your first commit to gather feedback early and prevent premature merges. Draft status clearly signals the work is incomplete, allowing collaborators to review direction without blocking other work or triggering CI/CD gates meant for final review.

Yes, you can standardize workflows by documenting conventional branch prefixes, PR templates, and merge readiness checks. Scripts and CI/CD hooks enforce naming rules and require draft PRs before commits reach main, reducing manual enforcement and human error.

Skipping draft PRs increases integration surprises, reduces collaboration opportunities, and bypasses early feedback cycles. This Skill enforces the draft PR requirement for non-trivial work to ensure every significant change receives review and team visibility before merging.