# branching-strategy-stinger

branching-strategy-stinger selects a Git branching workflow, handles hotfix routines, and resolves merge versus rebase questions based on your delivery cycle.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 96 repo stars
- Author: Legion Code Inc.
- License: AGPL-3.0-or-later · policy=link-only · description only; the file stays with the author
- Source: https://github.com/legioncodeinc/vibe-coding-tools/tree/HEAD/plugins/wasp-nest-core/skills/branching-strategy-stinger/SKILL.md
- Updated: 2026-10-18
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/branching-strategy-stinger

## What it does

This skill acts as an advisory assistant for version control architecture. Before suggesting any model, it checks your deployment schedule, team size, multi-version support needs, and existing repository files such as `.github/` configurations.

The logic strictly opposes long-lived branches. It directs standard web projects toward GitHub Flow or trunk-based development, reserving GitFlow solely for multi-version products like mobile SDKs or desktop apps. A core policy rule dictates that any task exceeding two working days before merging requires feature flags.

After finalizing decisions, the skill writes a complete repository guide to `docs/engineering/branching-policy.md`. It defines conventions and branch protections on paper, delegating actual repository API changes to companion tools.

## Install

### Claude Code (native platform)

1. **Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add legioncodeinc/vibe-coding-tools
```
In the agent chat (not a shell):
```text
/plugin install wasp-nest-core@wasp-nest
```
This installs the whole wasp-nest-core plugin with all its skills

2. **Skills CLI (Vercel)**
```bash
npx skills add legioncodeinc/vibe-coding-tools --skill branching-strategy-stinger -a claude-code
```

3. **Manually: put the files in place**
- File: `~/.claude/skills/branching-strategy-stinger/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/branching-strategy-stinger/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add legioncodeinc/vibe-coding-tools --skill branching-strategy-stinger -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/branching-strategy-stinger/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add legioncodeinc/vibe-coding-tools --skill branching-strategy-stinger -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/branching-strategy-stinger/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install legioncodeinc/vibe-coding-tools plugins/wasp-nest-core/skills/branching-strategy-stinger
```

2. **Manually: put the files in place**
- File: `.github/skills/branching-strategy-stinger/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add legioncodeinc/vibe-coding-tools --skill branching-strategy-stinger -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/legioncodeinc/vibe-coding-tools --path plugins/wasp-nest-core/skills/branching-strategy-stinger
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/branching-strategy-stinger/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/legioncodeinc/vibe-coding-tools/tree/HEAD/plugins/wasp-nest-core/skills/branching-strategy-stinger/SKILL.md

## When to use it
- Select between trunk-based development, GitHub Flow, and GitFlow
- Establish a predictable hotfix path for production bugs
- Reduce merge conflicts originating from stale feature branches
- Standardize squash, rebase, and merge commit rules
- Generate an engineering branching policy file for the repository

## Example prompts
- Review our deployment cadence and recommend a Git branching model
- Create a hotfix and release branch guide for our web application
- Audit our branch list to decide between feature flags and long-lived branches

## Similar
- [git-workflow-strategy](https://affpapa.org/en/nevibecode/skills/git-workflow-strategy.md) — skill · 489 installs
- [git-workflow-manager](https://affpapa.org/en/nevibecode/agents/git-workflow-manager.md) — subagent · 384 installs
- [git-workflow](https://affpapa.org/en/nevibecode/skills/devops-skills-git-workflow.md) — skill · 404 installs
- [Git Workflow taste](https://affpapa.org/en/nevibecode/prompts/git-workflow-taste.md) — prompt · ★ 178201 repo stars
- [gitflow](https://affpapa.org/en/nevibecode/rules/gitflow.md) — rule · ★ 41178 repo stars
- [flag-and-release-change](https://affpapa.org/en/nevibecode/skills/flag-and-release-change.md) — skill · 267 installs

From the same set: [legioncodeinc/vibe-coding-tools](https://affpapa.org/en/nevibecode/by/legioncodeinc/vibe-coding-tools.md) — 172 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
