skills.rest
muskie9
muskie9COMMUNITY
Explore all skills by this author →
WebsiteGitHub

ss-branch-strategy

Define branch naming conventions and default-branch rules for Silverstripe CMS upgrades.

Updated Jun 18, 2026
Search Tags:#branch naming#forking#default branch#Silverstripe#CMS upgrade
One-click install
npx skills add https://github.com/muskie9/agents --skill ss-branch-strategy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ss-branch-strategy
Source: https://github.com/muskie9/agents/tree/main/skills/ss-branch-strategy
Command: npx skills add https://github.com/muskie9/agents --skill ss-branch-strategy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the complexity of managing multiple versions of Silverstripe CMS during major version upgrades by establishing clear branch naming conventions and default-branch rules.

Core Features & Use Cases

  • Branch Naming Convention: Defines a consistent naming scheme for branches across all Silverstripe module repos during major CMS upgrades.
  • Default-Branch Rules: Outlines rules for maintaining active development branches and managing previous versions.
  • Preservation of Previous Versions: Ensures that previous major versions are preserved for backport fixes.
  • Forking Workflow: Provides guidelines for forking 3rd-party modules to support new CMS versions.
  • Auto-Merge Configuration: Explains how to set up auto-merge for integer default branches.

Quick Start

Set up your Silverstripe CMS upgrade by following the branch naming convention and default-branch rules outlined in the skill.

Frequently Asked Questions about ss-branch-strategy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage branch naming for a Silverstripe CMS major version upgrade?▼

Silverstripe CMS major version upgrades require consistent branch naming conventions across all module repos to maintain version control organization. This strategy defines a uniform naming scheme to streamline the upgrade process and prevent branch conflicts.

What is the default-branch strategy for maintaining previous Silverstripe CMS versions?▼

Default-branch rules outline maintaining active development branches while preserving previous major versions. This ensures prior Silverstripe CMS versions remain accessible for backport fixes alongside active development.

How do I fork third-party Silverstripe modules to support a new CMS version?▼

Forking third-party Silverstripe modules involves creating forks to support new CMS versions during upgrades. The workflow provides guidelines for managing these forks alongside your internal module repos.

Can I set up auto-merge for integer default branches in Silverstripe repos?▼

Auto-merge can be configured for integer default branches in Silverstripe repositories. The setup process is explained within the default-branch rules to automate merging across module repos.

When do I need a formal branch strategy for Silverstripe module upgrades?▼

A formal branch strategy is needed when managing multiple Silverstripe module repos during major CMS version upgrades. It addresses complexity by establishing clear forking workflows and default-branch rules.

Related Skills

Explore More Software Engineering Skills→
pradeepmoulipradeepmouli
2

speckit-git-initialize

Initialize a Git repository with configurable branch and .gitignore settings.

Community
Intermediate
muskie9muskie9

silverstripe-version-upgrade

Upgrade Silverstripe CMS projects across major versions with assessment and migration.

Community
Advanced
jsirishjsirish
1

silverstripe-module-ss6-upgrade

Automate Silverstripe module upgrades to version 6 with dependency and CI/CD handling.

Community
Advanced
lushly-devlushly-dev
4

manage-git

Orchestrate Git workflows for branching, releases, and parallel development.

Official
Advanced