neb-skills-upgrade

To detect drift in vendored skills, the workflow reads sources.yaml and executes nebcore-cli admin skills check-drift to identify configuration staleness against upstream sources. It then summarizes the detected changes for review.

The best way to upgrade vendored NebCore skills before a major release is orchestrating approved upgrades via full-replace, merge, or manual methods. This ensures compatibility with operator workflows and updates governance artifacts and changelogs.

The nebcore-cli integrates with the operator during skill upgrades by prompting for explicit operator approval where needed. This governance step ensures upstream changes are reviewed before being applied to the vendored configurations.

Yes, you can merge upstream changes instead of fully replacing vendored skills. The upgrade orchestration supports full-replace, merge, and manual upgrade methods to accommodate different configuration strategies and update changelogs accordingly.

You need to audit vendored skill configurations for staleness during drift checks, general audits, and before major NebCore releases. This ensures your vendored skills remain up-to-date with upstream sources defined in sources.yaml.

When manually upgrading vendored skills, the limitation is that you must independently resolve conflicts and update changelogs and governance artifacts without the automated full-replace or merge orchestration provided by the standard upgrade workflow.