skills.rest
sernafernando
sernafernandoCOMMUNITY
Explore all skills by this author →
GitHub

git-workflow

Guide Git Flow branching, conventional commits, and PR-based collaboration.

1|2|Updated Oct 1, 2025
Search Tags:#git#workflow#branching#pull-requests#git-flow#conventional-commits#pricing-app
One-click install
npx skills add https://github.com/sernafernando/pricing-app --skill git-workflow-sernafernando
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/sernafernando/pricing-app/tree/main/skills/git-workflow
Command: npx skills add https://github.com/sernafernando/pricing-app --skill git-workflow-sernafernando

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides structured guidance to implement a disciplined Git workflow for software projects, improving collaboration, traceability, and release quality.

Core Features & Use Cases

  • Branching guidance: Follow Git Flow conventions with feature, bugfix, refactor, and hotfix branches and clear main/develop roles.
  • Commit discipline: Use conventional commits and meaningful messages to create a clean, navigable history.
  • PR-based collaboration: Standardized pull requests, reviews, and merge strategies to streamline releases and code quality.

Quick Start

Follow a simple workflow: create a feature branch from develop, implement changes, commit with conventional messages, push, open a PR to develop, and merge to main following the defined branch strategy.

Frequently Asked Questions about git-workflow

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

FAQPage Schema
How do I set up a Git workflow with feature branches and conventional commits?▼

A Git workflow using Git Flow creates feature, bugfix, refactor, and hotfix branches from develop, enforces conventional commit messages for clean history, and uses pull requests to merge changes back into main and develop releases.

What is the Git Flow branching strategy for team collaboration?▼

Git Flow is a branching strategy that separates main and develop branches, directing new work into feature, fix, refactor, or hotfix branches, and standardizes pull request reviews to streamline releases and improve code traceability.

How do I create a pull request to develop following Git Flow conventions?▼

Creating a pull request to develop involves branching from develop, implementing changes, committing with conventional commit messages, pushing the branch, and opening a standardized PR for review before merging to main.

Can I use this Git workflow guidance for hotfix and refactor branches?▼

Yes, this Git workflow guidance supports hotfix and refactor branches alongside feature and fix branches, applying standardized naming conventions, conventional commits, and pull request practices to manage changes across releases.

Does this Git Flow workflow require specific tools or dependencies?▼

No dependencies are required to follow this Git workflow guidance, which uses Bash as the allowed tool to instruct teams on branch naming, conventional commits, and pull request-based collaboration.

Related Skills

Explore More Software Engineering Skills→
markhazlettmarkhazlett
4

sync

Switch to the main branch and pull latest changes from the remote.

Community
Basic
tunneleventunneleven

c4flow:merge

Merge pull requests into the main branch with pre-merge checks and post-merge cleanup.

Community
Intermediate
3balljugglerYu3balljugglerYu

git-create-pr

Automate commit, push, and pull request creation for Git repositories.

Community
Advanced
FutureAtomsFutureAtoms
1

git-github-branch

Create and manage Git branches with standardized naming conventions.

Community
Intermediate