upgrade-setup

Upgrade Setup — Selective Best-Practice Refresh

Power-user / internal tool. Normal users run /checkup, which decides whether /upgrade-setup is the right action and invokes it automatically. Running /upgrade-setup directly still works — use it when you already know you want to re-apply current best practices.

Use this skill to bring an existing setup up to the current plugin's defaults without destroying user customizations. It is the non-audit counterpart to /audit-setup:

Skill	Read-only	Applies changes	Per-change confirmation	Backup
/audit-setup	yes	no	n/a	n/a
/upgrade-setup	no	yes	yes (y/n/all/skip-rest)	yes

This skill is a protocol. Run every pass in order. Do not skip passes, and do not apply changes before Pass 3 confirms each one.

Language

Detect language from the user's first message in this invocation and respond in it throughout. All file content written to disk stays in English (see the repo language rule in CLAUDE.md).

Argument parsing

The invocation may contain --dry-run anywhere in the argument string (as a flag, not a value).

• If present: set dry_run: true. Pass 4 prints every diff but writes no files.
• Otherwise: set dry_run: false. Pass 4 runs normally.

If any other argument is passed, ignore it silently (forward compatibility — do not error).

---

Pass 1 — Detect the existing setup

Step 1.1 — Read the meta file

Read ./.claude/onboarding-meta.json if it exists. Expected shape:

{
  "setup_type": "coding",
  "skills_used": ["coding-setup"],
  "plugin_version": "0.9.0",
  "installed_at": "2026-04-01T12:00:00Z",
  "upgraded_at": null
}

If the file parses and setup_type is a recognized slug (one of: coding, data-science, design, knowledge-base, devops, content-voice, office, research, academic-writing, web-development), set: