om-apply-upgrade-notes

Syncs installed tracker and browser descriptors with shipped upgrade notes while preserving local edits.

2.6k|159|Updated Mar 8, 2021
One-click install
npx skills add https://github.com/go-musicfox/go-musicfox --skill om-apply-upgrade-notes-go-musicfox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: om-apply-upgrade-notes
Source: https://github.com/go-musicfox/go-musicfox/tree/main/.agents/skills/om-apply-upgrade-notes
Command: npx skills add https://github.com/go-musicfox/go-musicfox --skill om-apply-upgrade-notes-go-musicfox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After upgrading a skills collection, the artifacts a previous skill run installed into your repository — tracker descriptors at .ai/trackers/<tracker>.md and browser-provider descriptors at .ai/browsers/<provider>.md — become stale, which can degrade or skip operations they do not define. This Skill reads the collection's UPGRADE_NOTES.md, diffs installed descriptors against the shipped versions, and brings them up to date without discarding local customizations. ## Core Features & Use Cases - Descriptor diffing and sync: Compares installed tracker and browser descriptors operation-by-operation against shipped versions, classifying each difference as missing, changed, locally edited, or local-only, and applies additive updates safely. - Local customization protection: Never silently overwrites sections a team has edited; shows both versions side by side and asks the operator to keep, replace, or merge, while always preserving local-only operations. - Config and upgrade-notes verification: Walks UPGRADE_NOTES.md entries, adds missing config keys to .ai/agentic.config.json with documented defaults, checks expected artifacts, and reports custom-provider gaps instead of inventing implementations. - Use Case: After running npx skills add to upgrade your agent pipeline skills, invoke this Skill to re-sync the installed GitHub tracker descriptor with newly shipped operations like attach-image-evidence, then review the uncommitted diff and a structured report of exactly what changed. ## Quick Start Apply the skills collection's upgrade notes to this repository and re-sync my installed tracker and browser descriptors, showing me a dry-run report first.

Frequently Asked Questions about om-apply-upgrade-notes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update installed tracker descriptors after upgrading a skills collection?

Run the upgrade-notes skill, which diffs your installed descriptor at .ai/trackers/<tracker>.md against the shipped version operation by operation. Missing operations are appended additively, unchanged stock sections are replaced, and locally edited sections require your explicit confirmation.

What happens to my local customizations when syncing descriptors?

Local customizations are never overwritten silently. Sections that differ from stock are shown side by side with the shipped version so you can keep local, take shipped, or merge by hand, and local-only operations are always preserved and listed in the report.

Can I preview the upgrade changes before applying them?

Yes, pass the --dry-run flag to print every change the skill would make without modifying any files. You can also use --yes to auto-apply purely additive changes while still requiring explicit answers for conflicting edits.

Does the skill support custom tracker or browser providers?

Custom providers are not auto-implemented. The skill diffs the shipped TEMPLATE.md against your custom descriptor and files a gap report listing every newly required operation with its contract text, drafting a section for your review only when you ask.

What happens if my config has no browser.provider key?

Older configs default to playwright, and the skill adds a browser.provider key set to playwright so existing behavior is preserved. It never silently switches a repository to a different provider such as agent-browser.

Why does the skill stop when .ai/agentic.config.json is missing?

Without the config there is nothing installed to upgrade, so the skill stops instead of auto-running setup. It points you to the om-setup-agent-pipeline skill to establish the pipeline configuration first.