rename-component

To rename a dlt toolkit component, you specify the target skill, command, or rule and its new name. The tool automatically finds and replaces all internal cross-references across markdown files, workflow definitions, and plugin manifests to maintain consistency.

When renaming a component in a dlt toolkit, the tool updates internal cross-references in markdown files, workflow definitions, and plugin manifest files. This ensures all mentions of the old component name are replaced with the new name throughout the project.

Yes, the component rename process includes a validation step to verify dlt toolkit integrity post-rename. This ensures that all internal cross-references are correctly updated and the toolkit remains consistent after the modification.

Before using a dlt component rename tool, you need the uv dependency installed in your environment. You also need an existing dlt toolkit with defined skills, commands, or rules that you intend to rename and update.

Manually renaming a dlt skill breaks workflows because internal cross-references in markdown files, workflow definitions, and plugin manifests are not automatically updated. Using an automated rename component tool finds and replaces these references to prevent broken links.

Automated refactoring is the safest way to rename rules in a dlt toolkit because it automatically updates all internal cross-references and validates toolkit integrity post-rename, preventing the broken references that manual find-and-replace often misses.