master-child-merge-discipline

SKILLFlujo de trabajocomunidad
v0.0.0tedgoldsteinMITActualizado hace 1 mFuente →

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 →
1Clientes
1Formatos
hace 1 mÚltima actualización
Skill
Autortedgoldstein
Versión0.0.0
LicenciaMIT
CategoríaFlujo de trabajo
Formatosskill.md
PromptNo publicado
Compatibilidad
Claude✓ Compatible
Cursor
Copilot
ChatGPT
Gemini
Acerca de

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)

Palabras clave
skillclaude