update-specialists

To reconcile specialists runtime drift across repositories, this Skill groups findings by repository and guides targeted or bulk updates after a dry-run review. It separates runtime package drift from managed asset drift to ensure safe multi-repo operator refresh checks.

The safest way to update stale specialist definitions and hooks is through a dry-run verification workflow. This Skill inspects drift, summarizes results, and waits for explicit operator confirmation before applying any refresh or prune actions to registry-managed files.

Yes, you can refresh xtrm-managed skills without losing user-owned overlays. This Skill enforces preservation rules that protect user overlays and avoids destructive changes unless explicitly approved during the update workflow.

Separate Category A and Category B handling is required to prevent mixing specialists runtime drift with xtrm-managed filesystem asset drift. This separation ensures operators diagnose and repair stale rules, skills, and hooks without cross-contaminating the two distinct update paths.

Yes, the drift refresh workflow supports bulk updates across many repositories. This Skill groups diagnostic findings across your workspace, allowing operators to perform targeted or bulk updates while maintaining post-update drift confirmation.

You should avoid automated drift reconciliation when user-owned overlays are present and lack explicit approval for destructive changes. This Skill requires dry-run verification and operator confirmation specifically to prevent unintended pruning or overwriting of preserved files.