skills.rest
Zoppy-crm
Zoppy-crmOFFICIAL
Explore all skills by this author →
WebsiteGitHub

branching

Standardize Git branch naming and pull request workflows with issue linkage.

Updated Mar 1, 2026
Search Tags:#git#workflow#github#pr review#branching#branch naming#pull-request
One-click install
npx skills add https://github.com/Zoppy-crm/.github --skill branching-zoppy-crm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: branching
Source: https://github.com/Zoppy-crm/.github/tree/main/skills/backend/branching
Command: npx skills add https://github.com/Zoppy-crm/.github --skill branching-zoppy-crm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent branch names, unclear PR scope, and oversized pull requests make reviews slow and break automatic project linking, causing delays in development and fragile release flows.

Core Features & Use Cases

  • Branch naming conventions: Clear patterns for milestone, task, and hotfix branches to ensure kebab-case, inclusion of issue numbers when required, and protected branch behavior.
  • Branch flow and linking: Defines how to create task branches from milestone branches, open PRs to milestone and staging, and use issue numbers in branch names so GitHub Projects link and PR keywords close issues automatically.
  • PR size policy & best practices: Guidance on target PR size, how to slice large changes, review expectations, and rules to avoid direct pushes to protected branches.
  • Use Case: When implementing a new coupon feature, create a milestone branch for the feature, spawn task branches for each subtask with the issue number in the name, open focused PRs for each task, and then open a final PR from the milestone to staging.

Quick Start

Create a task branch from the corresponding milestone branch named task/coupon-engine/456-create-endpoint, open a PR to milestone/coupon-engine with a concise description and include the phrase Closes #456 in the PR body.

Frequently Asked Questions about branching

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

FAQPage Schema
How do I standardize branch naming conventions for GitHub pull requests?▼

Standardize branch naming conventions by enforcing kebab-case patterns for milestone, task, and hotfix branches while including required issue numbers. This ensures automatic GitHub Project linking and allows PR keywords to close issues automatically, keeping workflows consistent.

What is the best way to slice large pull requests for faster code review?▼

The best way to slice large pull requests is to spawn individual task branches from a milestone branch for each subtask, then open focused PRs targeting a specific size policy. This keeps reviews focused and prevents oversized changes from delaying the release flow.

How do I link a GitHub issue to a branch for automatic project tracking?▼

Link a GitHub issue to a branch by including the issue number directly in the branch name, such as task/coupon-engine/456-create-endpoint. This enables automatic GitHub Project linking and allows PR keywords like Closes #456 to close the issue when merged.

Can I open pull requests directly to staging from a task branch in Git?▼

Task branches should open PRs to their corresponding milestone branch rather than directly to staging. Once all task PRs are merged into the milestone branch, a final PR is then opened from the milestone branch to staging to consolidate the feature.

Why do I need branch protection rules for milestone and staging branches?▼

Branch protection rules are needed to prevent direct pushes to milestone and staging branches, ensuring all changes go through pull request reviews. This maintains review speed, protects fragile release flows, and enforces the standardized PR workflow.

Related Skills

Explore More Software Engineering Skills→
Clay-HHKClay-HHK
2

git-workflow

Provide standardized Git workflow guidance for commits, branching, merging, and tagging.

Community
Intermediate
oxieoxie

staging-deployment-phase

Automate staging deployment with auto-merge for merged pull requests.

Community
Intermediate
gralwebgralweb

create-pr

Generate GitHub pull requests from branch commits using GitHub CLI.

Community
Advanced
andymaiandymai
20

pr-workflow

Automate pull request workflows with AI review gates and GitHub releases.

Community
Advanced