cleanup-legacy-install

Detects and removes legacy clauDNA overlay files from ~/.claude/ after plugin migration.

Updated May 3, 2026
One-click install
npx skills add https://github.com/Claudfather/clauDNA --skill cleanup-legacy-install-claudfather
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cleanup-legacy-install
Source: https://github.com/Claudfather/clauDNA/tree/main/skills/cleanup-legacy-install
Command: npx skills add https://github.com/Claudfather/clauDNA --skill cleanup-legacy-install-claudfather

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Users who installed clauDNA before it became a marketplace plugin have stale skill, agent, and hook copies in ~/.claude/ that shadow the plugin-installed versions, causing outdated behavior and confusion. ## Core Features & Use Cases - Discovery-Based Detection: Enumerates the plugin's shipped components and only flags matching-name files in the legacy overlay, leaving user-created files untouched. - Customization Safety Check: Diffs each legacy file against the plugin version and requires per-file confirmation for anything that differs, so user modifications are never silently deleted. - Backup Before Removal: Copies the full removal manifest to a timestamped backup under ~/.local/share/clauDNA/backups/ before deleting anything. - Use Case: After installing the claudna plugin via the marketplace, run this skill to clean up the old install.sh overlay, fix a stale statusLine path in settings.json, and verify /claudna: skills resolve to the plugin copies. ## Quick Start Ask the assistant to clean up the legacy clauDNA install from ~/.claude/ now that the marketplace plugin is installed.

Frequently Asked Questions about cleanup-legacy-install

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I remove an old clauDNA install after switching to the plugin?

Run the cleanup-legacy-install skill after installing the claudna plugin. It detects legacy overlay files in ~/.claude/, diffs them against the plugin versions, backs everything up, and removes confirmed items.

Will the cleanup delete my customized skills or hooks?

No. Files that differ from the plugin's version are flagged individually, and you choose Keep or Remove for each one after viewing the diff. Nothing customized is deleted without explicit confirmation.

Can I restore files after the cleanup runs?

Yes. Before any deletion, the skill copies the full manifest to a timestamped directory under ~/.local/share/clauDNA/backups/. Restore any item with cp -r from that backup path back into ~/.claude/.

Why does my statusLine break after removing legacy hooks?

The old install pointed statusLine.command at ~/.claude/hooks/statusline.sh, which the cleanup removes. The skill detects this and offers to repoint the path to the plugin cache copy or remove the statusLine key entirely.

What happens if the plugin is not installed when I run the cleanup?

The skill stops immediately. It needs the plugin's component list as its discovery manifest, so it instructs you to install the plugin via the marketplace first and then re-run the cleanup.