agentsclimarketplace

Git branch strategy

Skill planifest/planifest-framework/planifest-framework/external-skills/git-branch-strategy

A specification framework for agentic development. Agents build from complete specs - not guesses.

Install
npx -y skills add planifest/planifest-framework --skill git-branch-strategy

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Define branch topology, lifecycle rules, and merge policy that match team delivery and release risk. Use when branch protection, release/hotfix flow, and merge discipline must be explicit to prevent unsafe history changes; do not use for CI workflow design or application behavior implementation.

SKILL.md

2.4 KB, 421 tokens by cl100k_base, as published. Nobody here has run it

Git Branch Strategy

Overview

Use this skill to design a branch model that teams can operate consistently under normal delivery and incident pressure.

Scope Boundaries

  • Use this skill when the task matches the trigger condition described in description.
  • Do not use this skill when the primary task falls outside this skill's domain.

Shared References

  • Existing governance baseline:
    • references/git-governance-contract.md
  • Topology decision guidance:
    • references/branch-topology-decision-rules.md

Templates And Assets

  • Branch policy template:
    • assets/branch-policy-template.md
  • Branch protection checklist:
    • assets/branch-protection-checklist.md

Inputs To Gather

  • Team size, collaboration style, and review ownership model.
  • Release cadence, hotfix urgency expectations, and support windows.
  • Branch protection capabilities on the hosting platform.
  • Current pain points (long-lived drift, merge conflicts, unclear ownership).

Deliverables

  • Branch class policy with creation/deletion/merge rules.
  • Protection rules mapped to branch criticality.
  • PR synchronization policy by branch class.
  • Operational guidance for hotfix and release scenarios.

Workflow

  1. Define branch classes and responsibilities in assets/branch-policy-template.md.
  2. Choose topology using references/branch-topology-decision-rules.md.
  3. Set merge direction and sync policy per branch class.
  4. Configure protection and verify with assets/branch-protection-checklist.md.
  5. Publish policy with concrete examples for common workflows.

Quality Standard

  • Branch classes are minimal, non-overlapping, and enforceable.
  • Protection rigor matches branch risk (stable > release > feature).
  • Merge/sync strategy is clear enough to avoid per-PR ambiguity.
  • Hotfix path is explicit and does not bypass traceability.

Failure Conditions

  • Stop when branch classes overlap without clear operational purpose.
  • Stop when policy requires controls that the hosting platform cannot enforce.
  • Escalate when hotfix process conflicts with protection and compliance requirements.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.