Agent skill

Gitflow

Branching, merging, versioning, and release conventions for the Gitflow workflow, covering main/develop branches, feature/release/hotfix branches, semantic versioning, and pull request rules.

Apache-2.0Auto-check passedDevelopment

Install Gitflow

skills CLI

$ npx skills add Mindrally/skills --skill gitflow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Mindrally/skills gitflow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Mindrally/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/gitflow .claude/skills/gitflow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "gitflow" agent skill from https://github.com/Mindrally/skills/tree/main/gitflow into .claude/skills/gitflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitflow", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Mindrally/skills/tree/main/gitflow

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Mindrally/skills --skill gitflow -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Mindrally/skills gitflow --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Mindrally/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/gitflow .agents/skills/gitflow && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "gitflow" agent skill from https://github.com/Mindrally/skills/tree/main/gitflow into .agents/skills/gitflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitflow", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Mindrally/skills --skill gitflow -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Mindrally/skills gitflow --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Mindrally/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/gitflow .cursor/skills/gitflow && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "gitflow" agent skill from https://github.com/Mindrally/skills/tree/main/gitflow into .cursor/skills/gitflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitflow", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Mindrally/skills.git --path gitflow

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Mindrally/skills --skill gitflow -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Mindrally/skills gitflow --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Mindrally/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/gitflow .gemini/skills/gitflow && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "gitflow" agent skill from https://github.com/Mindrally/skills/tree/main/gitflow into .gemini/skills/gitflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitflow", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Mindrally/skills gitflow

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Mindrally/skills --skill gitflow -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Mindrally/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/gitflow .github/skills/gitflow && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "gitflow" agent skill from https://github.com/Mindrally/skills/tree/main/gitflow into .github/skills/gitflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitflow", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Mindrally/skills --skill gitflow -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Mindrally/skills gitflow --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Mindrally/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/gitflow .opencode/skills/gitflow && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "gitflow" agent skill from https://github.com/Mindrally/skills/tree/main/gitflow into .opencode/skills/gitflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitflow", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: gitflow
GitHub stars: 267
Token cost: ~1.3k tokens
SKILL.md length: 649 words
Files: 1
Skills in repo: 34
Repo updated: Sep 3, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Branching, merging, versioning, and release conventions for the Gitflow workflow, covering main/develop branches, feature/release/hotfix branches, semantic versioning, and pull request rules.

Works in 6 steps: Sync develop — Run git checkout develop… → Create the feature branch — Run git… → Commit with conventional messages — Use… → …
Creating a branch
SKILL.md covers Workflow for a Feature Change, Main Branches, Supporting Branches and Commit Messages, plus 5 more sections
Calls git

What it does

Gitflow is an agent skill from Mindrally/skills. Branching, merging, versioning, and release conventions for the Gitflow workflow, covering main/develop branches, feature/release/hotfix branches, semantic versioning, and pull request rules. Use when creating a branch, naming a branch, planning a release or hotfix, writing a commit message, or setting up branch protection for a repository that follows Gitflow.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Git workflow, Commit messages and Pull requests. It works with Git. The repository describes itself as: 255+ Claude Code skills converted from Cursor rules. Expert coding guidelines for every major framework and language. The licence is Apache-2.0.

When your agent uses it

Creating a branch
Naming a branch
Planning a release
Writing a commit message

Example prompts

“/gitflow”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

Sync develop — Run git checkout develop && git pull origin develop so the feature branches from the latest development state.
Create the feature branch — Run git checkout -b feature/123-user-authentication, using the naming convention…
Commit with conventional messages — Use type(scope): description for every commit (see Commit Messages below).
Rebase or merge develop in — Before opening a PR, bring the branch up to date: git fetch origin && git rebase origin/develop (or merge…
Open a pull request into develop — Require at least one approval and passing CI checks; never commit directly to develop.
Merge and clean up — After merge, delete the feature branch both locally and on the remote: git branch -d feature/123-user-authentication…

What it can do on your machine

Read from SKILL.md and the folder at commit 9718410. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Gitflow loads about 1.3k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 649 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~93
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Mindrally/skills at commit 9718410, republished under its Apache-2.0 licence (© Mindrally). 649 words, ~1,341 tokens.

Download SKILL.mdSave it as .claude/skills/gitflow/SKILL.md (or your agent's skills folder).

name: gitflow
description: Branching, merging, versioning, and release conventions for the Gitflow workflow, covering main/develop branches, feature/release/hotfix branches, semantic versioning, and pull request rules. Use when creating a branch, naming a branch, planning a release or hotfix, writing a commit message, or setting up branch protection for a repository that follows Gitflow.

Gitflow

This skill covers the Gitflow branching model: the two long-lived branches, the three supporting branch types, commit message conventions, semantic versioning, and the release and hotfix processes.

Workflow for a Feature Change

Sync develop — Run git checkout develop && git pull origin develop so the feature branches from the latest development state.
Create the feature branch — Run git checkout -b feature/123-user-authentication, using the naming convention feature/[issue-id]-descriptive-name.
Commit with conventional messages — Use type(scope): description for every commit (see Commit Messages below).
Rebase or merge develop in — Before opening a PR, bring the branch up to date: git fetch origin && git rebase origin/develop (or merge, per team convention).
Open a pull request into develop — Require at least one approval and passing CI checks; never commit directly to develop.
Merge and clean up — After merge, delete the feature branch both locally and on the remote: git branch -d feature/123-user-authentication && git push origin --delete feature/123-user-authentication.

Main Branches

main (or master)

Contains production-ready code only.
Never commit directly to main.
Only accepts merges from hotfix/* branches or release/* branches.
Must be tagged with a version number after every merge (e.g. git tag -a v1.2.0 -m "Release 1.2.0").

develop

The main integration branch; contains the latest delivered development changes.
Source branch for all feature/* branches.
Never commit directly to develop — all changes land through pull requests.

Supporting Branches

feature/*

Branch from: develop.
Merge back into: develop.
Naming convention: feature/[issue-id]-descriptive-name (e.g. feature/123-user-authentication).
Must be up to date with develop before opening a PR.
Delete after merge.

release/*

Branch from: develop.
Merge back into: main and develop.
Naming convention: release/vX.Y.Z (e.g. release/v1.2.0).
Scope is limited to bug fixes, documentation, and release-oriented tasks — no new features.
Delete after merge.

hotfix/*

Branch from: main.
Merge back into: main and develop.
Naming convention: hotfix/vX.Y.Z (e.g. hotfix/v1.2.1).
Reserved for urgent production fixes only.
Delete after merge.

Commit Messages

Use Conventional Commits format: type(scope): description.

Type	Meaning
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation changes
`style`	Formatting, missing semicolons, etc. — no logic change
`refactor`	Code restructuring without behavior change
`test`	Adding or correcting tests
`chore`	Maintenance tasks (build scripts, dependency bumps)

Example:

feat(auth): add refresh-token rotation

fix(orders): prevent duplicate charge on retry

chore(deps): bump lodash to 4.17.21

Semantic Versioning

Given a version MAJOR.MINOR.PATCH:

MAJOR — incremented for incompatible/breaking API changes.
MINOR — incremented for backwards-compatible new functionality.
PATCH — incremented for backwards-compatible bug fixes.

Show full SKILL.md (269 more words)Show less

Pull Request Rules

All changes must go through pull requests — no exceptions for main or develop.
Minimum of one required approval before merge.
All CI checks must pass.
No direct commits to protected branches (main, develop).
The branch must be up to date with its target before merging.
Delete the branch after merge (both local and remote copies).

Branch Protection Rules

Apply to both main and develop:

Require pull request reviews before merging.
Require status checks to pass before merging.
Require branches to be up to date before merging.
Include administrators in the restrictions (no bypassing rules with elevated permissions).
No force pushes.
No branch deletions.

Release Process

Create a release branch from develop: git checkout -b release/v1.2.0 develop.
Bump version numbers in package manifests / changelogs.
Fix any release-specific issues (docs, last-minute bugs) — do not add new features.
Open a PR from the release branch into main.
After merge to main:
- Tag the release: git tag -a v1.2.0 -m "Release 1.2.0" and push the tag.
- Merge main back into develop so develop has the release commit and tag.
- Delete the release branch.

Hotfix Process

Create a hotfix branch from main: git checkout -b hotfix/v1.2.1 main.
Fix the production issue with the smallest possible change.
Bump the patch version.
Open a PR from the hotfix branch into main.
After merge to main:
- Tag the release: git tag -a v1.2.1 -m "Hotfix 1.2.1" and push the tag.
- Merge main back into develop so the fix isn't lost in the next release.
- Delete the hotfix branch.

Files

Just SKILL.md in gitflow of Mindrally/skills.

Open the folder on GitHubat commit 9718410

Compare with similar skills

Gitflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Gitflow compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Gitflow this skillMindrally/skills	267	—	~1.3k	Automated safety check: Pass	Apache-2.0	1 mo ago
Git Workflow and Versioningaddyosmani/agent-skills	102k	2 repos	~3.5k	Automated safety check: Notes	MIT	4 days ago
React Router Pull Request Creatorremix-run/react-router	57k	—	~2.5k	Automated safety check: Pass	MIT	today
Emoji Commit ConventionsbaptisteArno/typebot.io	11k	—	~424	Automated safety check: Pass	Custom licence	yesterday
Draft Pull Request Creatorwordpress-mobile/WordPress-Android	3.2k	—	~881	Automated safety check: Notes	GPL-2.0	today
Adk Gitgoogle/adk-python	22k	—	~1.3k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
102k GitHub starsUsed in 2 repos~3.5k tokens
DevelopmentAuto-check: notes
React Router Pull Request Creator
remix-run/react-router
Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.
57k GitHub stars~2.5k tokensUpdated today
DevelopmentAuto-check passed
Emoji Commit Conventions
baptisteArno/typebot.io
Sets the repository's convention for commit messages and pull request titles: one emoji prefix for the main intent, a concise title and clean follow-up commits.
11k GitHub stars~424 tokensUpdated yesterday
DevelopmentAuto-check passed
Draft Pull Request Creator
wordpress-mobile/WordPress-Android
Commits and pushes current changes, writes a pull request title and body from the branch history and template, and opens a draft PR on GitHub after you approve it.
3.2k GitHub stars~881 tokensUpdated today
DevelopmentAuto-check: notes
Adk Git
google/adk-python
Official
Writes commit messages and pull request descriptions for the adk-python repository: Conventional Commits types and scopes, subject lines that say why a change was made, and the linked-issue and…
22k GitHub stars~1.3k tokensUpdated today
DevelopmentAuto-check passed
Git PR Flow
wgzhao/Addax
Standard branch, commit, and pull-request workflow for this repo.
1.4k GitHub stars~216 tokensUpdated today
DevelopmentAuto-check passed

Questions about Gitflow

What does Gitflow do?

Branching, merging, versioning, and release conventions for the Gitflow workflow, covering main/develop branches, feature/release/hotfix branches, semantic versioning, and pull request rules. Gitflow is an agent skill from Mindrally/skills. Branching, merging, versioning, and release conventions for the Gitflow workflow, covering main/develop branches, feature/release/hotfix branches, semantic versioning, and pull request rules.

When should I use Gitflow?

Gitflow fits situations like: creating a branch; naming a branch; planning a release; writing a commit message.

How do I install Gitflow in Claude Code?

Run `npx skills add Mindrally/skills --skill gitflow -a claude-code`. Or copy the skill folder (gitflow in Mindrally/skills) into .claude/skills/gitflow in your project. Claude Code loads it when a task matches its description.

How do I install Gitflow in Codex?

Run `npx skills add Mindrally/skills --skill gitflow -a codex`. Or copy the skill folder (gitflow in Mindrally/skills) into .agents/skills/gitflow in your project. Codex loads it when a task matches its description.

Can I use Gitflow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Mindrally/skills --skill gitflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gitflow, .gemini/skills/gitflow, .github/skills/gitflow and .opencode/skills/gitflow in your project.

What does Gitflow need to run?

Going by SKILL.md and its folder, Gitflow needs the command-line tools its instructions call (git).

Does Gitflow access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Gitflow safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Gitflow use?

Gitflow is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gitflow use?

About 1.3k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Gitflow?

Skills that share tags, products or a category with Gitflow: Git Workflow and Versioning (addyosmani/agent-skills, 102k stars), React Router Pull Request Creator (remix-run/react-router, 57k stars), Emoji Commit Conventions (baptisteArno/typebot.io, 11k stars) and Draft Pull Request Creator (wordpress-mobile/WordPress-Android, 3.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gitflow?

Mindrally (a GitHub organization) maintains it in Mindrally/skills, which has 267 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on September 3, 2026.

Source: Mindrally/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Gitflow

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Gitflow

Workflow for a Feature Change

Main Branches

main (or master)

develop

Supporting Branches

feature/*

release/*

hotfix/*

Commit Messages

Semantic Versioning

Pull Request Rules

Branch Protection Rules

Release Process

Hotfix Process

Files

Compare with similar skills

Similar skills

More from Mindrally/skills

Related

Questions about Gitflow