Basic usage
comet uninstall removes only Comet-managed files and preserves your own hooks and non-Comet configuration.
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 one workflow or both. If you remove only one, the other workflow and shared configuration stay in place, so no reinstall is required.
When removing Classic, you can separately choose whether to remove OpenSpec or Superpowers Skills. Both are unchecked by default to avoid deleting companion capabilities still in use. Automation mode (--force or --json) also does not remove these 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, and it 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.
