Use when a task changes ms-core or the top-level repository must point at a new ms-core commit, especially for coordinated fixes spanning both repositories or when the correct submodule commit and push order matters.
Handle coordinated changes between the top-level toolkit repository and ms-core/ without leaving the repositories out of sync. Use this skill whenever ms-core code is modified or the submodule pointer needs to advance safely.
Use this skill when:
ms-core/ are editedms-coreDo not use this skill for top-level-only changes.
git statusgit -C ms-core statusms-core as its own repository.
ms-corems-corems-core change inside the submodule repository.ms-core branch or target branch before touching the top-level pointer commit.git add ms-core.PYTHONPATH=ms-core/src.ms-core commit.git reports safe-directory or auth issues inside ms-core, report the exact blocker and stop.ms-core still needs its own commit first.For top-level validation, prefer:
PYTHONPATH=ms-core/src pytest tests/ -v --tb=short -x
For submodule coordination, confirm:
git -C ms-core rev-parse --short HEADgit diff --submodulereferences/ms-core-sequence.mdWhen reporting status, separate:
ms-core commit SHA and push state