update-skills

Updating installed skill branches from upstream requires preflight checks to ensure a clean working tree before applying non-destructive merges. The process validates remotes, applies updates, resolves conflicts, and runs build and test validation to report a concise summary.

Merging upstream changes safely involves controlled, non-destructive application of updates with preflight checks. The workflow detects new commits, lets you select which skills to update, and validates merges with build and test before reporting a concise summary.

Git merge conflicts during skill branch updates are resolved through a controlled workflow that applies updates non-destructively. Preflight checks validate remotes and the working tree, then conflicts are addressed during the merge and validate phase.

Build and test validation runs after merges are applied to skill branches from upstream. This enforcement of a safe workflow validates that updates do not break existing functionality before reporting a concise summary of the update process.

Preflight checks before merging upstream changes ensure a clean working tree and correct remotes, preventing error-prone updates. These guardrails validate the environment before attempting non-destructive merges, avoiding conflicts and failed builds during skill updates.

Detecting new commits upstream for installed skills involves identifying available updates and letting you choose which to update. The process checks each installed skill branch against its upstream remote to determine which have new commits ready to merge.