Purge SweetClaude

To safely remove hidden configuration directories, the purge skill identifies the .sweetclaude directory, recommends a backup branch, and requires a two-step user confirmation before executing shell commands to delete the artifacts.

The best way to reset project configuration files without data loss is using a purge process that verifies artifact existence and mandates a backup branch recommendation before any deletion occurs.

Yes, you can re-initialize your project environment after cleaning up configuration artifacts, as the purge process removes the .sweetclaude directory structure completely to restore a clean state.

Yes, the project cleanup process requires explicit manual confirmation before deleting files, implementing a two-step verification process to prevent accidental data loss.

You should create a backup branch before removing local project directories because the purge process executes standard shell commands that permanently delete the directory structure and its contents.

You should decommission configuration files from a specific repository when you want to completely remove the tool's footprint and reset the project configuration to start fresh.