factory-branching-strategy

Enforce concurrency locks and branching rules for source control operations.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/e2its/myrmion-AI-factory --skill factory-branching-strategy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: factory-branching-strategy
Source: https://github.com/e2its/myrmion-AI-factory/tree/main/.claude/skills/factory-branching-strategy
Command: npx skills add https://github.com/e2its/myrmion-AI-factory --skill factory-branching-strategy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the chaos of uncoordinated source control changes, preventing merge conflicts, accidental direct commits to protected branches, and concurrent file modification errors that disrupt team development workflows and introduce breaking changes to production codebases.

Core Features & Use Cases

  • Mandatory Concurrency Lock Protocol: Serializes all file modification operations across agents using feature or epic-scoped filesystem locks, preventing overlapping work and data corruption.
  • Automated Branch Management: Handles branch creation, checkout, and validation aligned with project rules, including epic-scoped shared branches for related features and per-increment branches for sliced feature implementations.
  • Enforced Merge Governance: Blocks direct merges to protected branches, requiring all changes to go through configurable pull request workflows with approval and CI validation rules.
  • Use Case: A team developing a multi-epic enterprise application uses this Skill to ensure all agents work on dedicated branches, acquire locks before modifying files, and submit changes via PRs, eliminating conflicting changes and broken main branches.

Quick Start

Use the factory-branching-strategy skill to automatically enforce concurrency locks, validate branch naming conventions, and block unauthorized direct commits to protected branches before any file modification work begins.

Frequently Asked Questions about factory-branching-strategy

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

FAQPage Schema
How do I prevent concurrent file modification conflicts in git branching workflows?

To enforce protected branch guardrails, block all direct merges to protected branches and require changes to go through configurable pull request workflows. This ensures all modifications pass approval and CI validation rules before integrating into the main codebase.

What is the best way to manage epic-scoped branches for sliced feature implementations?

Direct commits to protected branches disrupt team development workflows and introduce breaking changes to production codebases. Enforcing governance-aligned merge policies blocks unauthorized direct commits and requires pull requests to prevent accidental overwrites and maintain codebase stability.

How do I enforce pull request approval rules for protected branches?

Concurrency locks serialize file modification operations across agents using feature or epic-scoped filesystem locks, preventing overlapping work and data corruption. This protocol applies to all agent-driven file modifications and incremental feature slicing scenarios.

Does this branching strategy work with agent-driven source control modification operations?

This branching strategy handles branch creation, checkout, and validation aligned with project rules. It supports epic-scoped shared branches for related features and per-increment branches for sliced feature implementations, ensuring all agents work on dedicated branches.