Post-update check: which of my customizations does this release replace or collide with?

[GruperTal]

Omarchy 4.5 ships half of my hacks, and some of the rest will fight with it. An agent can sort out which, per machine.

Omarchy is meant to be bent: plugins, hooks, scripts, keybindings, /etc tweaks. Then a release ships the same thing, and the hack lingers or fights the new default. 4.5's release notes already list "new defaults that could collide with bindings of your own" by hand. An agent can check that for each machine, and decide what's still needed.

What it found on my machine (4.0.6 against 4.5):

Mine	4.5	Verdict
SUPER + M → Spotifast	SUPER + M minimizes to the dock	Conflict: Hyprland fires both
SUPER + W → close confirmation	new SUPER + Q close chord skips it	Conflict
compose:ralt	Right Alt push-to-talk	Conflict
hand-installed omasnap	default package (#9446)	Drop mine
Omapager, workspace-planner plugins	built-in notifications, per-monitor workspaces (#15655)	Drop after updating
Telegram theme	open PR #16732	Keep for now

How it works (repo): a read-only scanner inventories customizations and diffs them against upstream, with every commit tagged by the first release that has it. The agent verifies each lead in the source and writes a report: on dev, in an RC, totally custom, conflicts and recommendations, each with its receipt. It changes nothing until you pick, and it backs up before touching anything.

The proposal:

1. Ship it as an optional skill next to omarchy and diagnose-crash in default/agents/skills/.
2. After an update, offer it with an opt-in notification, something like "Check your customizations against this release?". It would open the default agent with the skill. Never run it automatically.

Try it today: git clone https://github.com/GruperTal/omarchy-still-need-it.git ~/.claude/skills/omarchy-still-need-it, then /omarchy-still-need-it.

Happy to send a PR if it fits.