git-workflow

Enforce branch-based workflows with Conventional Commits prefixes and draft PRs.

Updated Dec 20, 2025

Search Tags:#automation #git #workflow #branching #pull-request #conventional-commits

Ready to run

npx skills add https://github.com/francisfuzz/emoji_gen --skill git-workflow-francisfuzz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/francisfuzz/emoji_gen/tree/main/.claude/skills/git-workflow
Command: npx skills add https://github.com/francisfuzz/emoji_gen --skill git-workflow-francisfuzz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a disciplined branch-based workflow with mandatory draft pull requests for non-trivial work, reducing integration surprises and improving collaboration.

Core Features & Use Cases

Feature branches with conventional prefixes (feat/, fix/, docs/, etc.)
Draft PRs required before merging non-trivial changes
Clear, copy-paste commands and examples to standardize collaboration

Quick Start

Start by updating main, create a feature branch with a conventional name, push, and open a draft PR with the commands provided below:

git checkout main git pull origin main git checkout -b feat/add-emoji-filtering git push -u origin feat/add-emoji-filtering gh pr create --draft --title "feat: add emoji category filtering" --body "Initial draft PR for emoji category filtering"

Frequently Asked Questions about git-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce a branch-based workflow with pull requests for my team?▼

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.

What are conventional commits and why should I use them for branch names?▼

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.

How do I create and push a feature branch with the right naming convention?▼

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.

When should I use draft pull requests instead of regular PRs?▼

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.

Can I automate branch creation and PR workflows across my repository?▼

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.

What happens if I merge a non-trivial change without a draft PR?▼

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.