skf-rename-skill

Atomically renaming a skill requires updating SKILL.md, metadata.json, context-snippet.md, and provenance-map.json across all versions before removing the old name. This transactional update ensures all references are verified and safely materialized.

Transactional skill renaming is a safe update mechanism that fully materializes and verifies the new name across all files before deleting the old name. It is needed to prevent data loss and broken references during version management operations.

Updating SKILL.md and metadata.json during a skill rename is handled automatically by identifying all on-disk versions and applying file updates across the board. This automated update also covers context-snippet.md and provenance-map.json files.

Yes, the renaming process handles orphaned on-disk skill versions by identifying them and applying the transactional rename. It works alongside manifest-tracked versions to ensure every instance of the skill is updated atomically.

Before renaming a skill, you need proper version management knowledge to understand how manifest-tracked and orphaned on-disk versions interact. This ensures the atomic rename process correctly targets all existing skill instances.

A limitation of atomically renaming a skill is that it requires proper version management knowledge to execute correctly. The process strictly updates SKILL.md, metadata.json, context-snippet.md, and provenance-map.json, meaning untracked files are not handled.