neopjm109/agent.oliver/branch-strategy-planner

Claude Code and agent skill by neopjm109/agent.oliver

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Define the repository's branching model and protection contract — protected branches, work-branch naming, and integration policy (PR vs direct, merge vs cherry-pick default) — as the source of truth every other vcs skill honors. Produces a spec, not git operations.

Install

npx vskill@latest install neopjm109/agent.oliver/branch-strategy-planner

SKILL.md

The same SKILL.md was published earlier as neopjm109/agent.oliver/branch-strategy-planner.

Goal

Produce the branching model and branch-safe protection contract for the repository: which branches are protected, how work branches are named, and how work reaches protected branches. This is a design artifact consumed by the other vcs skills and by deployment/cicd-generator (which triggers on the resulting branches); it performs no git operations.

Inputs

yaml
branch_requirements:
model: trunk-based | gitflow # default trunk-based
protected: [main] # + develop for gitflow
integration: pr | direct # PR when a remote/host exists, else direct merge/cherry-pick
release: tag | branch # how releases are cut

Output

yaml
branch_strategy:
protected: [main] # never committed to / force-pushed directly
work_branch_pattern: "feat/<feature-id>" # also chore/, fix/, spec/
default_integration: merge | cherry-pick
integration_via: pr | direct
release_scheme: tag | branch
rules: [<the branch-safe operating contract, restated for this repo>]

Workflow

Step 1 — Choose the model

Pick trunk-based (single protected main) or gitflow (main + develop) from requirements.

Step 2 — Define naming and protection

Set the work-branch pattern and mark protected branches write-forbidden for direct commits/force.

Step 3 — Set integration policy

Decide merge vs cherry-pick default and PR-vs-direct (PR when a remote/host is configured).

Rules

  • Protected branches are never the direct target of commits or force operations — encode this explicitly.
  • Every generated/changed artifact lands on a work branch matching work_branch_pattern.
  • Output a spec only; branch creation/switching is repo-initializer/commit-applier, integration is branch-integrator.
  • Keep the contract consistent with what cicd-generator expects to trigger on.

Examples

Input:

yaml
branch_requirements: { model: gitflow, integration: pr, release: tag }

Output:

yaml
branch_strategy:
protected: [main, develop]
work_branch_pattern: "feat/<feature-id>"
default_integration: cherry-pick
integration_via: pr
release_scheme: tag
rules:
- "No direct commit or force-push to main/develop."
- "All work on feat/<id>; integrate to develop via PR (cherry-pick); release-tag from main."

Security

  • Security scanPassed, 100 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
5

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/neopjm109/agent.oliver/branch-strategy-planner/badge)](https://verified-skill.com/skills/neopjm109/agent.oliver/branch-strategy-planner)

Something wrong with this skill or its page? Tell us.