Agent skill · mindrally
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. 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.
What it needs
About 3k tokens when loaded.
What this skill does
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 1. Sync develop — Run git checkout develop && git pull origin develop so the feature branches from the latest development state. 2. Create the feature branch — Run git checkout -b feature/123-user-authentication, using the naming convention feature/[issue-id]-descriptive-name. 3. Commit with conventional messages — Use type(scope): description for every commit (see Commit Messages below). 4. 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). 5. Open a pull request into develop — Require at least one approval and passing CI checks; never commit directly to develop. 6. 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). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills mindrally/gitflow