Skip to main content
This page is the shortest onboarding path for the Comet CLI. Just three commands cover installation, checking, and recovery. For the full options of each command, see the advanced topics.

​
Prerequisites

  • Node.js 20+
  • npm/npx
  • Git
Since 0.4.0-beta.1, Comet is a pure Node runtime and no longer requires Bash, Git Bash, or WSL. macOS, Linux, and Windows use the same set of commands.

​
Step 1: Install Comet

Install the CLI globally: 
npm install -g @rpamis/comet

​
Step 2: Initialize the project

Run it in the project root: 
comet init
It detects your AI coding platform and installs OpenSpec, Superpowers, and Comet Skills. For a Chinese-language environment, we recommend: 
comet init --scope project --language zh
For CI or scripting environments, use non-interactive mode: 
comet init --yes --scope project --language zh --json
After initialization, we recommend running comet doctor once to confirm the installation is complete.

​
Step 3: Use these two commands day to day

​
Recovering your workflow: comet status

After a session is interrupted, check the status before continuing: 
comet status
It tells you the current active change, which phase it’s in, and the recommended next command. Then type /comet to continue — the Agent recovers from file state, not from memory.

​
Troubleshooting: comet doctor

If comet status shows something abnormal, or the installation looks off: 
comet doctor
It checks both project-level and global installations, platform directories, Skills, scripts, and active change status, and provides recovery hints.

​
Upgrade and uninstall

Upgrade to the latest version: 
npm install -g @rpamis/comet@latest
comet update --scope project --language zh
comet doctor
Uninstall (preserving your OpenSpec changes, design documents, and code): 
comet uninstall --scope project

​
FAQ

By default it detects the AI coding platform directories in the current project. Use --scope project for project-level only, or --scope global for a global install.
Run comet doctor first to check for a malformed .comet.yaml or missing evidence. After fixing, re-run status.
Since 0.4.0-beta.1, all scripts run through Node.js, so Windows no longer requires Git Bash or WSL.

​
Advanced topics

The basic path ends here. Below are the full command references grouped by scenario:
Advanced topicSuited for
comet initFull initialization options and component selection
comet statusFull status fields and runtime data
comet dashboardLocal read-only browser dashboard
comet doctorFull diagnostic scope and troubleshooting flow
comet updateUpgrade flow and language switching
comet uninstallSafe uninstall and scope control

​
Skill, evaluation, and publishing commands

These three groups of commands belong to advanced scenarios. Regular users typically use them indirectly through /comet-any:
Advanced topicSuited for
comet skillLocal Skill package management and advanced Skill runs
comet evalGeneral-purpose Skill evaluation entry point
comet publishSkill publishing and distribution
comet bundleAdvanced Bundle backend (auditing/debugging)
To create reusable Skills, start with Composing any Skill quickstart; to evaluate Skills, start with Evaluation quickstart.
Last modified on July 6, 2026