master-child-merge-discipline

SKILLWorkflowcommunauté
v0.0.0tedgoldsteinMITMis à jour il y a 3 moisSource →

When the master-child Track pattern is in play (one Master Trackfile + N Phase children + a long-lived master branch like `track-session-manager`), the canonical checkout MUST stay on `main` so the operator has a stable read-only inspection point. Use a dedicated worktree for the master branch — eve

Community-submitted skill. Not yet reviewed by the Forge team. Full prompt content may not be available.Request review →
1Clients
1Formats
il y a 3 moisDernière mise à jour
Skill
Auteurtedgoldstein
Version0.0.0
LicenceMIT
CatégorieWorkflow
Formatsskill.md
PromptNon publié
Compatibilité
Claude✓ Pris en charge
Cursor—
Copilot—
ChatGPT—
Gemini—
À propos

When the master-child Track pattern is in play (one Master Trackfile + N Phase children + a long-lived master branch like `track-session-manager`), the canonical checkout MUST stay on `main` so the operator has a stable read-only inspection point. Use a dedicated worktree for the master branch — every Phase merge, every Master Trackfile update (Children list, Child progress, Files-likely-affected)

Mots-clés
skillclaude

Aucune couverture des dépendances

Cette entrée ne publie aucun paquet npm : Forge n'a donc pas d'arbre de dépendances pour elle. C'est une lacune de couverture — pas une affirmation qu'elle n'a aucune dépendance.