educates-training-platform: Skill for Claude Code

Educates Git Workflow

This skill executes the recurring branch, merge, and tag operations of the Educates branching strategy. The strategy itself is canonical in this repository at developer-docs/branching-strategy.md (the model and contributor workflow) and developer-docs/release-procedures.md (the maintainer operations). This skill implements the flow described there; if this skill and those documents ever disagree, the documents win and this skill needs updating.

What you execute and what the user decides

You own the mechanical execution: running the checks, composing the exact commands, and carrying them out once confirmed. You do not make release-strategy judgement calls. Always ask, and never decide yourself:

• When feature freeze is declared.
• What the next version number is.
• Whether a fix needs back-porting, and to which support lines.
• Whether a support line should be opened at all.

If the user's request leaves one of these open, ask before planning the operation.

Assumptions

• git and the gh CLI are installed, and gh is authenticated.
• Use is interactive: you propose, the user confirms, you execute. This skill is not a fire-and-forget automation.

Canonical repository identity and context detection

The canonical repository is:

educates/educates-training-platform

Before any operation, determine which context you are in. Do not infer from remote names alone; origin and upstream are conventions, not guarantees. Read each remote's configured URL with git config --get remote.<name>.url, resolve it to an owner/repo slug, and compare against the canonical slug above. Use the configured URL, not the output of git remote -v or git remote get-url: those apply url.<base>.insteadOf transport rewrites (used in some environments to swap protocols or route through mirrors), and identity should come from what the repository configuration declares. Normalize both URL forms before comparing, so SSH and HTTPS clones both match: