ilk-upgradelisted

# ilk-upgrade — pull latest ilk-skills and make it effective A cross-platform command that: 1. **Resolves the active toolkit clone** from the script's own real (symlink-resolved) path — never from cwd, never hard-coded. 2. **Fetches and computes ahead/behind** against `origin/main` (`--check`, read-only). 3. **Applies the update** via `git pull --ff-only` and re-runs the installer when needed (`--apply`). 4. **Reports what changed** — commit log, file diff, and whether the installer was re-run. This command operates on the **toolkit clone** (the `ilk-skills` repo symlinked/junctioned into `~/.{cursor,claude,codex}/skills`), NOT on the project in your current working directory. ## When to use - The user says: `/ilk-upgrade`, `upgrade ilk`, `update ilk-skills`, `升级 ilk`, `ilk 更新`, `拉取最新`, `ilk-upgrade --check`, `ilk-upgrade --apply`. - Codex users may say: "upgrade ilk", "update the skills toolkit", "pull latest ilk-skills" without a slash prefix. - The user wants to check if the toolkit is behind origin (`--check`). - The user wants to pull the latest and make it effective (`--apply`). - The user wants to see what changed in the last update. ## Two staleness meanings There are two independent git repos in play: - **The toolkit clone** — this `ilk-skills` repo, symlinked/junctioned into `~/.{cursor,claude,codex}/skills`. "Stale" = behind `origin/main`. **This is what ilk-upgrade operates on.** - **The project being looped** — whatever cwd resolves