Basic usage
Comet inspects previously installed targets and removes files it owns. It avoids deleting user customization unless the prompt explicitly asks and you confirm.
Examples
Remove project-level Comet assets:
Preview machine-readable output for automation:
Remove Comet from every indexed project installation:
Choose workflows to remove
When a target has both Native and Classic installed, interactive uninstall lets you remove either workflow or both. Removing one keeps the other workflow and its shared configuration in place, so you do not need to install it again.
When you remove Classic, you can independently choose whether to remove the OpenSpec or Superpowers Skills. Both remain unselected by default to avoid removing companion Skills you still use. Automation with --force or --json keeps its existing full-uninstall behavior and does not remove those companion Skills automatically.
Choose the project uninstall scope
When indexed projects exist, interactive comet uninstall asks whether to operate on the current project or every indexed project. --json, --force, and explicit --current-project stay local. Cross-project uninstall requires --all-projects, which cannot be combined with --scope global or --current-project.
To remove only the global installation while indexed projects exist, bypass the project-scope selector explicitly:
Batch uninstall reports each project separately. If Comet-owned files cannot be removed safely, that project remains failed and stays indexed instead of being marked complete.
Uninstall removes only Comet-owned Skills, rules, hooks, and config fragments.
It preserves project code, OpenSpec changes, Design Docs, Plans, verification
reports, and unrelated third-party Skills.
