How do I install the Git Flow skill?

Run npx skillmds@latest add odjaramillo/git-flow-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Git Flow safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Flow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Git Flow free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Git Flow?

odjaramillo (@odjaramillo) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Git Flow by odjaramillo — Agent Skill

Name: Git Flow
Author: odjaramillo

File contents

Git Flow Strategy

When to Use

Deciding which branch to base work on.
Creating a new Release or Hotfix.
Merging strategies (Squash vs Merge Commit).

1. Branching Model

Branch	Source	Merge Into	Lifespan	Purpose
`main`	-	-	Infinite	Production-ready code. Stable.
`develop`	`main`	`main`	Infinite	Integration branch for next release.
`feature/*`	`develop`	`develop`	Short	New features (e.g., `feature/login-page`).
`release/*`	`develop`	`develop`, `main`	Medium	Release prep (e.g., `release/v1.0.0`).
`hotfix/*`	`main`	`develop`, `main`	Very Short	Production critical fixes (e.g., `hotfix/crash`).

2. Feature Development

Start: Update develop and branch off.

git checkout develop && git pull origin develop
git checkout -b feature/my-feature

Work: Commit changes. Use github skill templates for PRs.
Finish: PR into develop. Squash merge recommended.

3. Release Process

Start: Branch off develop when features are frozen.

git checkout develop
git checkout -b release/v1.2.0

Work: Bump versions, update changelogs, fix bugs. NO NEW FEATURES.
Finish:
- Merge into main (Tag this commit).
- Merge into develop (Back-propagate fixes).
- Delete release/v1.2.0 branch.

4. Hotfixes

Start: Branch off main (Production).

git checkout main
git checkout -b hotfix/critical-bug

Work: Fix the critical bug. Minimal changes.
Finish:
- Merge into main (Tag this commit).
- Merge into develop.
- Delete hotfix branch.

5. Protocols

Never commit directly to main or develop.
Keep history clean. Use interactive rebase before PRs.
Tags are immutable. Once pushed, do not change.

---name: git-flow-2description: Standard Git Flow branching model and lifecycle management strategy. Trigger: "create release", "hotfix", "branching strategy", "git flow".license: Apache-2.0---# Git Flow Strategy## When to Use- Deciding which branch to base work on.- Creating a new Release or Hotfix.- Merging strategies (Squash vs Merge Commit).## 1. Branching Model| Branch | Source | Merge Into | Lifespan | Purpose ||--------|--------|------------|----------|---------|| `main` | - | - | Infinite | Production-ready code. Stable. || `develop` | `main` | `main` | Infinite | Integration branch for next release. || `feature/*` | `develop` | `develop` | Short | New features (e.g., `feature/login-page`). || `release/*` | `develop` | `develop`, `main`| Medium | Release prep (e.g., `release/v1.0.0`). || `hotfix/*` | `main` | `develop`, `main`| Very Short| Production critical fixes (e.g., `hotfix/crash`). |## 2. Feature Development1. **Start:** Update `develop` and branch off. ```bash git checkout develop && git pull origin develop git checkout -b feature/my-feature ```2. **Work:** Commit changes. Use `github` skill templates for PRs.3. **Finish:** PR into `develop`. Squash merge recommended.## 3. Release Process1. **Start:** Branch off `develop` when features are frozen. ```bash git checkout develop git checkout -b release/v1.2.0 ```2. **Work:** Bump versions, update changelogs, fix bugs. NO NEW FEATURES.3. **Finish:** - Merge into `main` (Tag this commit). - Merge into `develop` (Back-propagate fixes). - Delete `release/v1.2.0` branch.## 4. Hotfixes1. **Start:** Branch off `main` (Production). ```bash git checkout main git checkout -b hotfix/critical-bug ```2. **Work:** Fix the critical bug. Minimal changes.3. **Finish:** - Merge into `main` (Tag this commit). - Merge into `develop`. - Delete `hotfix` branch.## 5. Protocols- **Never commit directly to `main` or `develop`.**- **Keep history clean.** Use interactive rebase before PRs.- **Tags are immutable.** Once pushed, do not change.

Frequently asked questions

Git Flow