Pulling Updates from Skills Repository

To sync a local skills repository with upstream changes while preserving personal edits, run the update workflow to fetch and merge commits. This git-based process uses stashing to safeguard local modifications during the synchronization.

When merging upstream updates causes conflicts, the process detects diverging branches and provides optional conflict resolution guidance. This minimizes disruption by helping you resolve mismatched commits while keeping your changes intact.

You can pull the latest versions from the skills repository manually during a session. The one-command update workflow streamlines pulling updates for manual refreshes or session starts to stay current.

The best way to keep a forked skills repo updated is using a deterministic git-based workflow. It performs status checks, stashing, fetch, and merge to align local branches with upstream changes automatically.

The upstream sync process requires no special git dependencies or components. It implements a deterministic git-based workflow including status checks, stashing, fetch, merge, and conflict guidance natively.

You should avoid automated git merge for repository synchronization when you have uncommitted changes that conflict heavily, although the process does stash local edits to preserve them before fetching and merging.