migrate-to-skills

To migrate Cursor rules and slash commands, run the migration workflow to convert eligible .cursor/rules/*.mdc and .cursor/commands/*.md files into standardized SKILL.md entries under .cursor/skills, preserving the original body content verbatim while adding frontmatter.

Eligible Cursor rules for migration include those that have a description but lack both globs and alwaysApply settings. All slash commands are eligible for migration regardless of their configuration.

Migrating slash commands preserves the original body verbatim while creating frontmatter with name and description. This ensures consistent discovery and reuse across project and user workspaces without altering the original logic.

The migration process handles both project and user scopes, creating destination skill directories under the appropriate scope. It safely ignores internal worktrees and reserved paths like ~/.cursor/skills-cursor during the transformation.

Converting .mdc rule files into standardized SKILL.md entries under .cursor/skills enables consistent discovery, reuse, and portability across projects. The migration applies safe model invocation settings and ignores internal worktrees for repeatable transforms.

Internal worktrees and reserved paths like ~/.cursor/skills-cursor are explicitly ignored during the rules to skills conversion. This ensures safe, repeatable transforms without modifying internal configuration directories.