What problem does it solve? Renaming a session category in the AI Agents Orchestrator dashboard only edits the shared config, which orphans every existing session because their folders, notes frontmatter, and active-sessions entries still point at the old name. This Skill performs the actual migration so nothing is left dangling. ## Core Features & Use Cases - Dry-run planning: Validates that the old category exists and the new name is free and valid, then prints the folder move, the number of notes to re-tag, active-sessions entries, and any running sessions before touching anything. - Full migration: Moves the category folder, rewrites the category: line in every session's notes.md frontmatter, updates matching entries in ~/.claude/active-sessions.json (including notes_path), and renames the category in the config while keeping its color and scope. - Safety guards: Refuses to run when a category name exists under multiple spaces, aborts if the destination folder already exists, warns about running sessions whose working directory would go stale, and writes all JSON atomically. - Use Case: You want to rename your FEAT category to FEATURE across a dozen sessions. Run the plan step, confirm no sessions are running, then apply — every reference is migrated in one pass. ## Quick Start Ask the assistant to rename category FEAT to FEATURE, review the dry-run plan it shows, and confirm to apply the migration.
